-
Notifications
You must be signed in to change notification settings - Fork 43
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 missing cpid in userinfo #992
Comments
Also running into this issue. I can replicate it consistently, only happens when account is new and you need to first click "Authorize", then no matter how many times you retry, /userinfo doesn't return a cpid and only returns { sub }. (if you restart entire sign in flow then it finally works, but this is not ideal for users forcing them to retry signing in) |
I have also started to notice this happening. @tisbells any knowledge of this, we are seeing multiple signups with no |
I also had these issues a lot recently… |
Oh no, @DarkIntaqt is there any rioters that we know of who we can tag? I feel like this has been getting worse. |
afaik they are a heavily short staffed atm, and while I agree with you that this has a pretty high priority, I don't know whether there is anyone who is actively in charge of / monitoring the Github. |
I think you are right, the only developer l have seen who has replied on some github issues is: @lucasMesquitaBorges, any chance we could get some eyes on this. I've also submitted a ticket on this: 108409707 |
Hi! That's correct. Thanks for the ping in this thread. |
Hey @lucasMesquitaBorges any update on this? We are now seeing around 1 in 3 requests without a For now we have resorted to just spamming the summoner endpoint for each region to find out which region they might belong to, which is not ideal but gives up an alternative for now. |
The To continue triaging this issue we will need to get some sensitive information. @OllieJennings since you provided a ticket ID, we will contact you via zendesk to get more information and find the root cause. |
@lucasMesquitaBorges yep exactly that, we are finding that we find the "shard" by looping through all regions and requests their summoner based on their More that happy to give all required details when needed, will keep an eye out for the ticket response. Update: have responded back to the ticket with the relevant info |
Hi all! Can you please detail what scopes you're including in the redirect url for user authorization? |
I'm facing the same issue on my application. The scopes I'm using are: |
cpid is missing from the response from
https://auth.riotgames.com/userinfo
cpid scope IS specified.
normally
https://auth.riotgames.com/userinfo
returns { sub, cpid, jti } but just getting { sub }Not every account is affected. It may only be for new accounts. I am unsure when this bug started occurring.
The text was updated successfully, but these errors were encountered: