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
Switch BattleNet to OIDC #4015
Switch BattleNet to OIDC #4015
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nextauthjs/next-auth/hSaq7uBf7MfqU9ACkGf6hzu5mZKw [Deployment for 8571a03 canceled] |
I'm new to next-auth btw so still finding my feet. I've noticed account linking only works when you have the same email address (and you're logged in when the flow starts). Battlenet doesn't return an email address 🤷 I assume to do account linking here i need to wait for the api (next release?) |
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.
Thanks, I left some comments to clean the config up.
As proof, could you also take a screenshot of your logged-in user so we know it actually works? Good to have as a future reference.
This is correct. The default linking probably won't change, but you can use the |
Co-authored-by: Balázs Orbán <info@balazsorban.com>
Co-authored-by: Balázs Orbán <info@balazsorban.com>
Co-authored-by: Balázs Orbán <info@balazsorban.com>
Locally where would the most appropriate place for me to do that be? For context i'm trying to sign in using Credentials but then link several oauth'd accounts. |
Should be a discussion, not a comment on this PR 😉 |
I standardized the changes of this PR in a follow-up commit here: 163149b Basically, we should be using |
Running into |
Reasoning 💡
The current battlenet provider is broken, this switches it to a OIDC provider instead.
It switches it to a typescript file from a js file too.
Checklist 🧢
Affected issues 🎟
Fixes: #4013