single sign on - What can cause Identity Provider initiated SSO to fail -
we wrote our own identity provider on sharepoint server , saml 2.0 looks pretty good. posting third party service provider on same network. post base 64 encoded. have setting in web.config asks if saml encoded or not, , if no , encoded, documentation indicates supposed log error indicating such. since there no error logged, assuming failing in cross-site post. hitting sso consumer page log urlreferer , correct machine listed initiating sso...
what might causing this?
it turns out control name setting in service provider web.config incorrect because of asp.net naming convention control bearing samlresponse when set runat="server"
in identity provider.
Comments
Post a Comment