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

Introspection response must return `scope` instead of `scopes`. #852

Closed
yuriyz opened this Issue Jul 16, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@yuriyz
Contributor

yuriyz commented Jul 16, 2018

Introspection response must return scope instead of scopes.

Based on spec : https://tools.ietf.org/html/rfc7662#section-2.2

@yuriyz yuriyz added the bug label Jul 16, 2018

@yuriyz yuriyz added this to the 3.1.4 milestone Jul 16, 2018

@yuriyz yuriyz self-assigned this Jul 16, 2018

yuriyz added a commit that referenced this issue Jul 16, 2018

#852 : added correct `scope` field to introspection response. `scopes…
…` field is deprecated and has to be removed in 4.0.0 version. We left it to not break existing functionality.

#852
@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Jul 16, 2018

Fixed in 3.1.4 and master.

yuriyz added a commit that referenced this issue Jul 16, 2018

#852 : added correct `scope` field to introspection response. `scopes…
…` field is deprecated and has to be removed in 4.0.0 version. We left it to not break existing functionality.

#852

(cherry picked from commit d7420e1)

yuriyz added a commit that referenced this issue Jul 16, 2018

@yuriyz yuriyz closed this Jul 16, 2018

yurem added a commit that referenced this issue Aug 9, 2018

syntrydy pushed a commit that referenced this issue Sep 22, 2018

yuriyz
Revert "#852 : removed `scopes` field from 4.0.0 version (it was left…
… in earlier versions only for compatibility)."

This reverts commit f335d07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment