tag:blogger.com,1999:blog-9265269.post112234742178523639..comments2023-09-19T04:42:21.193-07:00Comments on xmldap: Interesting post at sforcecmorthttp://www.blogger.com/profile/07365195237862694751noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-9265269.post-1124900634690968162005-08-24T09:23:00.000-07:002005-08-24T09:23:00.000-07:00Thanks for the comments!Infocard has potential, bu...Thanks for the comments!<BR/><BR/>Infocard has potential, but at the moment, we've got a ways to go before its a viable approach.<BR/><BR/>In terms of meta-data exchange, we'd need this to be relative to the identity of the invoker, so the client would at least need to emit the salesforce org in which the user resides. The policy would need to be dynamic based upon that.cmorthttps://www.blogger.com/profile/07365195237862694751noreply@blogger.comtag:blogger.com,1999:blog-9265269.post-1124895656381446382005-08-24T08:00:00.000-07:002005-08-24T08:00:00.000-07:00Two Solutions:1/ InfoCard system. Windows will hel...Two Solutions:<BR/><BR/>1/ InfoCard system. Windows will help you selecting the InfoCard and hence and the client application will know whom to talk to get the SAML token.<BR/><BR/>2/ You can write your client in such a way that before doing the invocation of web service it retrieves its policy & metadata and there lies the information which identity provider to invoke to get the SAML token.<BR/><BR/>Regards<BR/>http://www.dotnetcard.com/Blogs/ksachdeva/Anonymousnoreply@blogger.com