Reuse old aspx routes in Blazor
We are writing a new version of an old page that other pages are dependent on. As such it’s important to keep old routing.
We are writing a new version of an old page that other pages are dependent on. As such it’s important to keep old routing.
I am quite new to Blazor and I am trying to understand authentication and authorization. What I did so far is reading the docs Authentication and Authorization in ASP.NET Core Blazor and Rolebased Authorization in Asp.NET Core. I managed to get authentication running, but I am struggeling with authorization. I would like to store every windows user who is visiting my server side app in a database and say User1 is Admin, User2 is Editor etc. and showing users diffrent areas of pages.
In an ASP.NET Blazor App with Identity I have a page with the page routing
I’ve created a template Blazor Server Side project in VS with single tenant Azure AD authentication. Running the app on localhost i’m able to log in fine, but unable to log in when the app is published as Azure Web app. Error: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: ‘app client id here’.
Environments Asp.Net Core 5.0 Blazor WebAssembly App (Asp.Net Core Hosting) Asp.Net Core Identity (with Identity Server 4) Problem I want to use Role-based authorization between Server side and Client side. I can login correctly and UserManager.IsInRoleAsync(user, “admin”) returns True in the Server side. But neither @attribute [Authorize(Roles = “admin”)] nor <AuthorizeView Roles=”admin”> doesn’t work in … Read more
I have a simple Blazor server side application that logs in a user using the microsoft-identity-web 0.2.1-preview package.
I did the following (It should work but it does not), no redirect, no error, no nothing, it just displays the page without auth, what am I doing wrong?
After implementing openidconnect, where does blazor store the access token? how to retrieve it?