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.

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

Remove redundant scope parameter #15382

Merged
merged 1 commit into from
Dec 15, 2022

Conversation

lukasz-walkiewicz
Copy link
Member

@lukasz-walkiewicz lukasz-walkiewicz commented Dec 13, 2022

Description

According to https://www.rfc-editor.org/rfc/rfc6749#section-4.1.3 scope parameter in the get token request is actually redundant as it was already provided in the authorization request. Refresh token request on the other hand should still provide it.

Additional context and related issues

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

@cla-bot cla-bot bot added the cla-signed label Dec 13, 2022
According to https://www.rfc-editor.org/rfc/rfc6749#section-4.1.3 scope
parameter in the get token request is actually redundant as it was
already provided in the authorization request. Refresh token request on
the other hand should still provide it.
@kokosing
Copy link
Member

Remove redundant scope parameter from OAuth2 authorization code grant get token request.

What is the user visible impact? The RN you suggested is more about what changed in implementation, while RN should be about UX.

@lukasz-walkiewicz
Copy link
Member Author

There are no-user visible changes in that case.

@kokosing kokosing merged commit 4bf5d5e into trinodb:master Dec 15, 2022
@kokosing
Copy link
Member

Merged. Thanks

@github-actions github-actions bot added this to the 404 milestone Dec 15, 2022
@lukasz-walkiewicz lukasz-walkiewicz deleted the redundant-scope branch December 16, 2022 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants