Closed xperiandri closed 5 years ago
just add nuget Microsoft.AspNetCore.Components.Authorization to your client
@agusibrahim, but it is present. As you can see from csproj contents above Did I miss something else?
@xperiandri besides seeing the message, does the rest actually work, or not? The only change we've made in this area during Preview9 was to increase log level. If this is not working for you, feel free to provide us a minimal repro project so that we can look into it, when we get time.
@xperiandri besides seeing the message, does the rest actually work, or not?
It does not work. At least AuthorizeView
uses NotAuthorized
part.
OK, I'll create a repro
@mkArtakMSFT, could you give your email? I will send repro privately
@xperiandri could you share a minimal repro and post it on Github?
@mkArtakMSFT, have a look into Gitter private messages
@pranavkm, well I would prefer to show my real project in private. And if it does not help then create simple repro. I can't see anything difficult running of my project on any environment. It only has authentication, nothing else special
We would prefer a simple repro. Thanks!
My issue was caused by Fluxor state reducers not being called and AuthenticationStateProvider.NotifyAuthenticationStateChanged
not being invoked
Describe the bug
After I updated Blazor WASM from preview8 to preview9 I get
DefaultAuthorizationService Authorization failed
in browser console Could you tell how to fix or how to find a root cause?To Reproduce
App.razor
AuthenticationStateProvider
implementationExpected behavior
Information in browser console is enough to determine the cause of authentication fail https://github.com/aspnet/AspNetCore/issues/7789
Additional context
Project file