-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Closed
Labels
DoneThis issue has been fixedThis issue has been fixedarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.feature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssembly
Milestone
Description
If you have this:
builder.Services.AddApiAuthorization();Then things work fine. But if you have this:
builder.Services.AddApiAuthorization(options => { });... then you get an exception like this:
Microsoft.JSInterop.JSException: Could not load settings from '_configuration/Microsoft.AspNetCore.Components.WebAssembly.Authentication'
Clearly the client name is wrong. And I think it's because of this line:
Line 64 in 9078b35
| services.AddRemoteAuthentication<RemoteAuthenticationState, TProviderOptions>(); |
Shouldn't it instead be the following?
AddRemoteAuthentication<RemoteAuthenticationState, OidcProviderOptions>(services, configure);Looks like there's a similar bug here too.
Also this suggests we're short on E2E test coverage.
Or am I misunderstanding how this API is meant to work?
Metadata
Metadata
Assignees
Labels
DoneThis issue has been fixedThis issue has been fixedarea-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.feature-blazor-wasmThis issue is related to and / or impacts Blazor WebAssemblyThis issue is related to and / or impacts Blazor WebAssembly