-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
DocsThis issue tracks updating documentationThis issue tracks updating documentationarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssembly
Milestone
Description
I am trying to do setup a client-side Blazor (ASP.NET Core Hosted) project with a third-party OAuth2 login provider, but the current documentation for authentication and authrorization doesn't cover this use-case.
The scenario requires me to only use the third-party login provider, without any other identity source.
The current MVC approach involves a challenge call that redirects to the third-party provider and returns the token. This approach doesn't seem to work with Blazor. Therefore, additional documentation would be helpful.
Tiberriver256, PassiveModding, rysep2, vcrobe and iraqforlife
Metadata
Metadata
Assignees
Labels
DocsThis issue tracks updating documentationThis issue tracks updating documentationarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor Componentsfeature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssembly