fix: add user-agent to patreon oauth requests #20305
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does it do?
The users & permissions plugin has a provider for logging in via Patreon. Recently requests to Patreon started to fail with a 400 error. It appears to be because of the lack of a
User-Agent
header in the requests. This PR adds theUser-Agent
header similar to the existing GitHub provider.See a related discussion including Patreon's response at https://www.patreondevelopers.com/t/status-400-https-www-patreon-com-api-oauth2-v2-identity/8836/9.
Why is it needed?
Without this PR, logging in via Patreon always fails.
How to test it?
GET
request toapi/auth/patreon/callback
with the data that Patreon sends back in the URL redirection. This request should return the correct user.Related issue(s)/PR(s)
N/A