Skip to content

Conversation

@esneilm
Copy link

@esneilm esneilm commented Jan 3, 2019

When validating audience scope you check for the token to be an authentication token in line 65, but introspection is an OAuth2.0 spec (https://tools.ietf.org/html/rfc7662) meaning that you will have non related user token (when refering to client credentials grant). This validation is great but should be only for user related tokens.
On the other hand one of the purpose of introspection endpoint is to provide what rights of access the token carries adding scope to the members of the response should be included. https://tools.ietf.org/html/rfc7662#section-2.2

juanifioren and others added 7 commits September 29, 2018 13:24
Fixed juanifioren#285 -- Ensured standard and custom claims can be used at the same time when using the OIDC_IDTOKEN_INCLUDE_CLAIMS setting
…an be used at the same time when using the OIDC_IDTOKEN_INCLUDE_CLAIMS setting"
Revert "Fixed juanifioren#285 -- Ensured standard and custom claims can be used at the same time when using the OIDC_IDTOKEN_INCLUDE_CLAIMS setting"
@juanifioren juanifioren changed the base branch from master to develop January 4, 2019 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants