Added idToken: true to Battlenet provider

[Stono]

Part fixes: #4013

Reasoning 💡

To help fix the battlenet provider

Checklist 🧢

• [ ] Documentation
• [ ] Tests
• Ready to be merged

Affected issues 🎟

#4013

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nextauthjs/next-auth/6v2KTkxxB7MfPUrDvikYKFFULoPh
✅ Preview: Canceled

[balazsorban44]

Looks like there is a much easier solution, they support OIDC:

https://develop.battle.net/documentation/guides/using-oauth/oidc-endpoints

See for example https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/auth0.ts on how to configure OIDC.

idToken: true won't be necessary either then, since #3514

These changes will most likely fix #4013 entirely 👍

[Stono]

Looks like there is a much easier solution, they support OIDC:

https://develop.battle.net/documentation/guides/using-oauth/oidc-endpoints

See for example https://github.com/nextauthjs/next-auth/blob/main/packages/next-auth/src/providers/auth0.ts on how to configure OIDC.

idToken: true won't be necessary either then, since #3514

These changes will most likely fix #4013 entirely 👍

Yip exactly the route i was going down! I will close this issue and PR another

[Stono]

@balazsorban44 opened a new PR over at #4015