Blazor Wasm Authentication (MSAL): Not waiting for token

Question

Hi,

I have a standalone Blazor Webassembly app (.NET 6) with authentication implemented with Azure AD, using MSAL.

In Program.cs, I am using the following auth configuration:

builder.Services.AddMsalAuthentication(options =>  
{  
    var scopes = builder.Configuration.GetValue<string>("AzureAd:Scopes");  
  
    options.ProviderOptions.DefaultAccessTokenScopes.Add(scopes);  
  
    builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication);  
});  

For the rest of the app's auth configuration, I have the same setup as described in standalone-with-azure-active-directory.

The issue is that, when logging in using the "redirect" login mode, even after successfully logging in, when the user is redirected back to the app from Microsoft's login page, the app thinks the user is still unauthenticated. If the user then subsequently hits refresh, the app successfully logs the user in.

Any help with this issue would be much appreciated as I've been dealing with it for a while now.

Thanks

Answer 1

Hi @Moinuddin Mohamed ,

Thanks for reaching out.

I have tried the sample application mentioned in the document and added "redirect" login in program.cs as below. I am successfully able to redirect to application after login using "redirect" in same way as popup.

builder.Services.AddMsalAuthentication(options =>  
{  
    ...  
    options.ProviderOptions.LoginMode = "redirect";  
});  

As mentioned by @Moinuddin Mohamed , the issue here is due to redirect URL has not been configured properly while registering the application due to which user is not able to access that URL.

Thanks,
Shweta