Cannot register all BattleNet Provider Regions at the same time. about aspnet.security.oauth.providers HOT 5 CLOSED

Each instance would need a different CallbackPath so they don't get mixed up.

from aspnet.security.oauth.providers.

Now that you mention it I remember that that they wanted to do some kind of unified server.
But thanks @Tratcher for the info, I knew there was something I missed / didn't understand correctly.
That problem would have been too common, even though that provider is probably not that common.

I will certainly take a look at OpenIddict, it looks really interesting.

Thanks for the quick answer!

from aspnet.security.oauth.providers.

It's worth noting that there's now a unified oauth.battle.net server that covers all regions except China. We may want to update the aspnet-contrib provider to use oauth.battle.net by default and fall back to oauth.battlenet.com.cn for China.

Note: the OpenIddict Battle.net integration already uses the unified server + their OIDC-capable login flow, if you're interested in giving it a try (more info here if you're not familiar with the OpenIddict web providers: https://kevinchalet.com/2022/12/16/getting-started-with-the-openiddict-web-providers/).

from aspnet.security.oauth.providers.

Proposed change to use the global server as part of our v8.0.0 release is here: #813

from aspnet.security.oauth.providers.

Support for the unified server will be part of our imminent 8.0 release.

from aspnet.security.oauth.providers.