You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
In a setup with a PingFederate IdP we're seeing that IdentityServer2 redirects to /account/signin?ReturnUrl=%2fissue%2fwsfed after PingFederate posts back the WS-Fed + SAML assertion data to IdentityServer2. I have no idea where to start looking or what possibly is going wrong, so if anyone can give any pointer on where to start looking, that would be great.
As a side-note, for an other customer we already have a successful setup but, unfortunately, I cannot compare the WS-Fed/SAML data.
The text was updated successfully, but these errors were encountered:
In a setup with a PingFederate IdP we're seeing that IdentityServer2 redirects to
/account/signin?ReturnUrl=%2fissue%2fwsfed
after PingFederate posts back the WS-Fed + SAML assertion data to IdentityServer2. I have no idea where to start looking or what possibly is going wrong, so if anyone can give any pointer on where to start looking, that would be great.As a side-note, for an other customer we already have a successful setup but, unfortunately, I cannot compare the WS-Fed/SAML data.
The text was updated successfully, but these errors were encountered: