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

[BUG] RSO Login ‘Invalid or expired authorization code, Redirection URI mismatch or PCKE verification failure’ #999

Open
ramezsw opened this issue Oct 14, 2024 · 2 comments

Comments

@ramezsw
Copy link

ramezsw commented Oct 14, 2024

Bug Description
When trying to login through the Riot single sign-on page, the login fails and returns the below error in the redirect URI response.

‘Invalid or expired authorization code, Redirection URI mismatch or PCKE verification failure’

Problem Description
The API Key used is fine and not expired. It's been working for many months, only started to fail on ~October 13th.

Expected Result
Upon successfully logging in using Riot Account credentials, users should be authenticated in the third-party app.

Actual Result
Call to redirect URI fails with 400 Error code, with the error mentioned above.

Developer Impact
Consistent frequency on any log in attempt. Using different browesrs/incognito is not fixing the issue. Also manually entering the riot username/pass instead of login with google etc is not working.

  • Frequency: Consistent, on any attempt to Sign in with Riot.
  • Severity: Users cannot link their Riot accounts on our platform.

Preconditions
N/A

Has there been any changes in the RSO endpoints recently? We could not find any documentation changes online, however, sites like tracker.gg were showing the same error starting October 13th. But it appears that issue is now fixed on tracker.gg

@xorth
Copy link

xorth commented Oct 15, 2024

Can confirm we are experiencing this too. (Tracker.gg)

@ramezsw
Copy link
Author

ramezsw commented Oct 15, 2024

Thanks for looking into this. We managed to find a solution to issue in www.gamerg.gg by changing the parameter structure of /token endpoint, it seems the structure of the Bearer token is a bit different starting from 13th October, which was causing the error.

The RSO API doc has no mention of any recent changes, so we're not sure what changed behind the scenes to start causing the issue, but we found our workaround/solution by trying out different methods as documented in this RFC https://www.rfc-editor.org/rfc/rfc6749#section-4.1.3

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

No branches or pull requests

2 participants