Skip to content
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.

Sign up for GitHub

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

Jump to bottom

oauth2: Expire consent request on successful consent interaction #771

Closed
aeneasr opened this issue Feb 7, 2018 · 0 comments
Closed

oauth2: Expire consent request on successful consent interaction #771

aeneasr opened this issue Feb 7, 2018 · 0 comments
Assignees
@aeneasr
Labels
feat New feature or request.
Milestone
1.0.0-alpha.1

Comments

@aeneasr
Copy link
Member

aeneasr commented Feb 7, 2018

No description provided.

@aeneasr aeneasr added the feat New feature or request. label Feb 7, 2018
@aeneasr aeneasr added this to the 1.0.0-alpha1 milestone Feb 7, 2018
@aeneasr aeneasr self-assigned this Feb 7, 2018
@aeneasr aeneasr mentioned this issue May 2, 2018
Closed
4 tasks
aeneasr pushed a commit that referenced this issue May 4, 2018
oauth2: Improves the consent flow design
c19df71 
This patch makes significant changes to the consent flow. First,
the consent flow is being renamed to "User Login and Consent Flow"
and is split into two redirection flows, the "User Login Redirection Flow"
and the "User Consent Flow".

Conceptually, not a lot has changed but the APIs have been cleaned up
and the new flow is a huge step towards OpenID Connect Certification.

Besides easier implementation on the (previously known as) consent app,
this patch introduces a new set of features which lets ORY Hydra
detect previous logins and previously accepted consent requests. In turn,
the user does not need to login or consent on every OAuth2 Authorize Code
Flow.

This patch additionally lays the foundation for revoking tokens per
user or per user and client.

Awesome.

Closes #771
Closes #772
aeneasr pushed a commit that referenced this issue May 4, 2018
oauth2: Improves the consent flow design
a002e30 
This patch makes significant changes to the consent flow. First,
the consent flow is being renamed to "User Login and Consent Flow"
and is split into two redirection flows, the "User Login Redirection Flow"
and the "User Consent Flow".

Conceptually, not a lot has changed but the APIs have been cleaned up
and the new flow is a huge step towards OpenID Connect Certification.

Besides easier implementation on the (previously known as) consent app,
this patch introduces a new set of features which lets ORY Hydra
detect previous logins and previously accepted consent requests. In turn,
the user does not need to login or consent on every OAuth2 Authorize Code
Flow.

This patch additionally lays the foundation for revoking tokens per
user or per user and client.

Awesome.

Closes #771
Closes #772
@aeneasr aeneasr closed this as completed May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aeneasr aeneasr

Labels
feat New feature or request.
Projects
None yet
Milestone
1.0.0-alpha.1
Development

No branches or pull requests
1 participant
@aeneasr