-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
feat(auth): OAuth2 access_token in GET query string in userInfoURL #5188
Conversation
I'm still thinking about adding only a prop in the definition.yml instead. My solution might create backward-compatibility issues (well, only if someone relies on using an |
This should indeed be optional and off by default. |
@NGPixel Applied your suggested modifications, tested it manually with fresh database with my oauth2 config, worked very well. |
this._oauth2._useAuthorizationHeaderForGET = true | ||
} else { | ||
this._oauth2._useAuthorizationHeaderForGET = false | ||
url.searchParams.set('access_token', accesstoken) |
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.
You're creating an url
variable, set a searchParams but then it's never used again? Am I missing something?
Also the current default would cause existing installations to suddenly use the opposite behavior. Either set the useAuthorizationHeader default as true or reverse the logic...
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.
Completely forgot about the url variable. Will reverse the logic. Thx for the review gonna mend the things and test them again.
See #5187
Small patch for using older OAuth2 authorization servers