Repository navigation
Authorize always redirects to LoginURL even when auth request is already authenticated (SSO/session use-case) #833
Unanswered
mohammadlashkari
asked this question in
Q&A
Replies: 1 comment
|
I’d really appreciate it if someone could guide me on this. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I’m implementing a custom OIDC provider using
github.com/zitadel/oidc/v3and adding session-based SSO (browser login sessions).In my implementation, when a user already has a valid session, I mark the auth request as authenticated inside
Storage.CreateAuthRequesthowever theAuthorizehandler always does:This causes a redirect to the login UI even when the user already has a valid session and the auth request is already authenticated
Questions
When a valid session already exists, should the flow be short-circuited inside
Storage.CreateAuthRequest, or is it only expected to mark the request as authenticated and let the caller handle redirection?Should the
Authorizehandler detect an already authenticated auth request and redirect directly to the callback instead of always redirecting to the login UI?Is there a recommended pattern for handling sessions and SSO?
Any guidance or documentation pointers would be appreciated. Thanks!
All reactions