Discord Provider StackOverflowException about aspnet.security.oauth.providers HOT 2 CLOSED

Fixed by adding Cookie authentication and setting it as the default authentication scheme.

See: dotnet/aspnetcore#42975

from aspnet.security.oauth.providers.

Note: this stupid bug was introduced in .NET 7.0 when the ASP.NET team decided to always default to the single authentication handler available when only one is registered in the pipeline: in this case, the Discord handler tries to delegate the persistence of the user identity to another handler, but the ASP.NET Core authentication stack doesn't find one and returns the only handler available: Discord. It does that until it stack-overflows... 🤣

If you don't need to persist the user identity in a cookie (e.g you just want to perform a one-shot action on behalf of the user after he approves the connection), the OpenIddict client and its Discord integration won't require registering a cookie handler. You can learn more about the OpenIddict providers here: https://kevinchalet.com/2022/12/16/getting-started-with-the-openiddict-web-providers/

from aspnet.security.oauth.providers.