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 Sep 18, 2021. It is now read-only.
A WS-Federation based external IdP might call the "core/callback" endpoint directly without calling "core/connect/authorize" before. There is a problem with this scenario, because the Cookie "idsrv.signin.message" is not set. Would it be possible to set the SignInMessage from Get Parameters in the "core/callback" or a new endpoint? Or is there an other possibility to solve this problem.
Current Scenario:
[External IdP] ----(WsFed - Saml)----> [IdentityServer(core/callback)] ---(Jwt)---> [APP]
External IdP calls the IdentityServer "core/callback" Endpoint with a Saml-Token. The IdentityServer Authenticate it via "Microsoft.Owin.Security.WsFederation.WsFederationAuthenticationMiddleware" and redirect the Jwt to the ReturnUrl from the SignInMessage. This approach works only if I set the Cookie manually by calling core/connect/authorize Endpoint before.
The text was updated successfully, but these errors were encountered:
A WS-Federation based external IdP might call the "core/callback" endpoint directly without calling "core/connect/authorize" before. There is a problem with this scenario, because the Cookie "idsrv.signin.message" is not set. Would it be possible to set the SignInMessage from Get Parameters in the "core/callback" or a new endpoint? Or is there an other possibility to solve this problem.
Current Scenario:
[External IdP] ----(WsFed - Saml)----> [IdentityServer(core/callback)] ---(Jwt)---> [APP]
External IdP calls the IdentityServer "core/callback" Endpoint with a Saml-Token. The IdentityServer Authenticate it via "Microsoft.Owin.Security.WsFederation.WsFederationAuthenticationMiddleware" and redirect the Jwt to the ReturnUrl from the SignInMessage. This approach works only if I set the Cookie manually by calling core/connect/authorize Endpoint before.
The text was updated successfully, but these errors were encountered: