-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implicit flow: id_token_hint, prompt=none #990
Comments
I imagine this could also be useful for enabling slient refresh, see for example this approach of |
hey @srenatus i know this one's a bit old, but has there been any further thought put into this feature? seems like a nice one to have |
@scotthew1 Sorry I had missed that last question for a while... uhm, I've added tags 😅 ...Help welcome! I still think it would be a cool enhancement, and not blowing up Dex' focus too much. |
From my limited understanding, this is what I would need in order to get refresh tokens working using my (implicit) flow. Does that sound plausible, or should I be using something else? |
The OpenID Connect Implicit Client Implementer's Guide 1.0 - draft 20 mentions in 2.1.1.1 Request Parameters:
This would make the interaction between the user (operating a web frontend) and their IdP more streamlined:
id_token
and anaccess_token
, and, when they've expired,/auth?id_token_hint=$EXPIRED_ID_TOKEN
,id_token
, and forward the user without presenting the connector selection.Am I missing something already existing in dex? I think I've poked around a bit, I couldn't find anything resembling login hints in the current code.
By any chance, is this on your roadmap? Also: would you like a PR? Or is this something you don't want dex to support?
Cheers
Stephan
The text was updated successfully, but these errors were encountered: