-
Notifications
You must be signed in to change notification settings - Fork 53
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
The token request should not include the scope parameter #130
The token request should not include the scope parameter #130
Conversation
Good stuff! 👍 But now that we have one example of an IDP that will fail with "scope" in, and non that require "scope" to be there. I'd say it's safe to remove it. |
ecf0a0e
to
32dbb28
Compare
The scope parameter is not indicated in RFC7636 for inclusion in the token request. It should be removed as it causes issues with strict IDP implementations.
32dbb28
to
fb9ad4c
Compare
I saw the tests had not ran. So I fixed that and rebased your branch. You can now see that they fail. |
I moved the optional scope field to the token refresh request type to correct that. I also updated the test data since the scope parameter is no longer sent in the token request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks for the contribution
The scope parameter is not indicated in RFC7636 for inclusion in the token request. It should be removed as it causes issues with strict IDP implementations.
What does this pull request change?
Removes "scope" parameter from token request
Why is this pull request needed?
Including "scope" is a specification violation
Issues related to this change
#129