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: Check application's granted audience on refresh #325

Closed
aeneasr opened this issue Oct 29, 2018 · 0 comments · Fixed by #332
Closed

oauth2: Check application's granted audience on refresh #325

aeneasr opened this issue Oct 29, 2018 · 0 comments · Fixed by #332

Comments

@aeneasr
Copy link
Member

aeneasr commented Oct 29, 2018

No description provided.

aeneasr added a commit that referenced this issue Nov 3, 2018
@aeneasr
oauth2: Improve refresh security and reliability
d1a831b 
This patch resolves several issues regarding the refresh flow. First,
an issue has been resolved which caused the audience to not be
set in the refreshed access tokens.

Second, scope and audience are validated against the client's
whitelisted values and if the values are no longer allowed,
the grant is canceled.

Closes #331
Closes #325
Closes #324
@aeneasr aeneasr mentioned this issue Nov 3, 2018
Merged
aeneasr added a commit that referenced this issue Nov 3, 2018
@aeneasr
oauth2: Improve refresh security and reliability (#332)
4e4121b 
This patch resolves several issues regarding the refresh flow. First,
an issue has been resolved which caused the audience to not be
set in the refreshed access tokens.

Second, scope and audience are validated against the client's
whitelisted values and if the values are no longer allowed,
the grant is canceled.

Closes #331
Closes #325
Closes #324
budougumi0617 added a commit to budougumi0617/fosite that referenced this issue May 10, 2019
@budougumi0617
oauth2: Improve refresh security and reliability (ory#332)
66f37e1 
This patch resolves several issues regarding the refresh flow. First,
an issue has been resolved which caused the audience to not be
set in the refreshed access tokens.

Second, scope and audience are validated against the client's
whitelisted values and if the values are no longer allowed,
the grant is canceled.

Closes ory#331
Closes ory#325
Closes ory#324
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

oauth2: Improve refresh security and reliability ory/fosite
1 participant
@aeneasr