After upgrading to a new mobile phone, your authenticator apps like Okta, Duo Mobile, Google Authenticator will need to be reset. The request needs to be started by the network admin. Okta Verify Network Admin needs to reset your Okta login. After the reset, the VPN login should prompt you to re-enroll on your next... » read more
To change the message “Authorizing…” Need to add to file App.razor Sources: https://docs.microsoft.com/en-us/aspnet/core/blazor/security/?view=aspnetcore-5.0#customize-unauthorized-content-with-the-router-component
Setup SendGrid Account Setup account at https://sendgrid.com/ Get API key. NuGet and install SendGrid to app. Blazor WebAssembly Setup Note: Add to “Server” project, not “Client” project. Need to setup user secrete for the application first. Add “SendGridUser” and “SendGridKey” user secrete to Server project. secrets.json Add classes to Services folder AuthMessageSenderOptions.cs EmailSender.cs Areas.Identity.Pages.Account.RegisterConfirmation page... » read more
Error: Publishing a new Blazor app with Identity to Azure App Service giving the following error: HTTP ERROR 500 Fix: Steps: Windows PowerShell (Admin mode) Manage computer certificates Certificates – Local Computer -> Personal -> Certificates Right click on certificate -> Export Enable Password and select “TripleDES-SHA1” Upload pfx file to Azure App Service Get... » read more
Issue: Authenticate state does not update after login when in main layout page, therefore IsInRole function does not work. Workaround: Force the browser to refresh.
AuthenticationStateProvider AuthenticationState AuthenticationStateProvider vs AuthenticationState Blazor has a built-in service called AuthenticationStateProvider service. This service obtains authentication state data from ASP.NET Core’s HttpContext.User. This is how authentication state integrates with existing ASP.NET Core authentication mechanisms. It is this service that is used by AuthorizeView component and CascadingAuthenticationState component to get the authentication state. Don’t use AuthenticationStateProvider directly. Use the AuthorizeView component. The main drawback to using AuthenticationStateProvider directly... » read more
1. Create new field of string type in the AspNetUsers table of Identity database. 2. Add field to ApplicationUser class. (Server) 3. Create new class called CustomUserClaimsPrincipalFactory 4. Add to ConfigureServices in Startup.cs (Server) Note: As soon as the line .AddClaimsPrincipalFactory<CustomUserClaimsPrincipalFactory>(); is added, role does not work anymore.
Note: Need to configure both .Client and .Server projects. .Client Create a new class called CustomUserFactory.cs Add to Main of Program.cs (Client) .Server Add to ConfigureServices of Startup.cs (Server) Result Index.razor (Client) OrgAdminOnly.razor (Client) Sources: https://docs.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-identity-server?view=aspnetcore-3.1&tabs=visual-studio
When configuring Blazor Identity … Error: NotSupportedException: Store does not implement IUserRoleStore<TUser>. var roles = await _signInManager.UserManager.GetRolesAsync(user); Fix: Add .AddRoles<IdentityRole>() to Configuration of Startup.cs