-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
oauth2: Remember authentication and application authorization #697
Labels
feat
New feature or request.
Milestone
Comments
OIDC compliant:
Simple (not OIDC compliant):
|
Consent flow in hydra
|
aeneasr
pushed a commit
that referenced
this issue
Dec 16, 2017
This commit aims at improving OpenID Connect conformity whilst making it as easy as possible to implement the consent app. For that reason, ORY Hydra is now capable of remembering user sessions and previous consent requests, and properly handles OpenID Connect's maxAge and prompt parameters. Additionally, public OAuth 2.0 clients always require the full consent flow. Closes #692 Closes #697
5 tasks
6 tasks
This is resolved on master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The goal of this issue is to make implementing an OIDC conformant consent app easier.
maxAge
,prompt=login
,prompt=none
andprompt=consent
andacr
accordingly.acr
should be the same asprompt=login
mustAuthenticateUser
indicates that the user must be logged out (if signed in already) and logged back in again. This should happen whenprompt=login
or when no user session existsmustAuthorizeConsent
indicates that the user must give his/her consent. This should happen whenprompt=consent
, when an unknown application requests authorization, or when new scopes are requestedrequestedAuthenticationContext
(Authentication Context Class Reference) indicates that some level of assurance was required. Setting this to anything other than empty or0
has the same effect asprompt=login
For starters, subject ID and authorized clients (+ scopes) could be stored in the encrypted session cookie, or alternatively in the consent manager.
The text was updated successfully, but these errors were encountered: