Blazor Wasm AAD B2C authentication issue

[ismailhozza]

Describe the bug

Hi, I am struggling with the below error. Can't figure out the root cause. I have a Blazor Wasm application with AAD B2C authentication. Login works fine, but after some time I get the below error. Any ideas what could be the problem?

Based on the console logs, it seems that ID token is undefined.

ClientAuthError: null_or_empty_id_token: The idToken is null or empty. Please review the trace to determine the root cause. Raw ID Token Value: undefined

Further technical details

• Dotnet version: 5.0.100
• Project dependencies

`

<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="5.0.1" PrivateAssets="all" />

<PackageReference Include="Microsoft.Authentication.WebAssembly.Msal" Version="5.0.1" />

<PackageReference Include="Microsoft.Extensions.Logging.Configuration" Version="5.0.0" />

<PackageReference Include="System.Net.Http.Json" Version="5.0.0" />

`

[mkArtakMSFT]

Thanks for contacting us.
Are you able to reliably reproduce this issue? If so, please share a small repro project so that we can investigate this.

[andersson09]

I get this error too, if I'm logged in and leave it for a while (around 30mins or so), then later refresh tab. In order to get the spa working again I need to close the session and open a new tab

[juho-hanhimaki]

I ran into this too after the initial token has expired (60 minutes?).

Just followed the steps in the documentation:
https://docs.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-azure-active-directory-b2c?view=aspnetcore-5.0

[juho-hanhimaki]

I did change the CacheLocation to localStorage (otherwise default template):

builder.Services.AddMsalAuthentication(options =>
{
options.ProviderOptions.Cache.CacheLocation = "localStorage";

Don't yet know if the change has something to do with the issue.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

[andersson09]

Hi, I don't think this should be marked as stale, there is clearly an issue as multiple people are receiving the same exception.

[juho-hanhimaki]

I did manually build a updated version of AuthenticationService.js which included patch #28498 AND updated the msal-browser library to 2.8.0 (#29010) (required some changes in the typescript source, but somehow got it working 😅).

Now the issue is gone for me. Don't know which one of those two things fixed the issue, but the main thing for me is that the issue seems to be gone with those steps.

[morganc9]

Hello,
I have exactly the same error on my blazor project using B2C... +1
It happen when I let my tab open too long. I guess it's an issue with the token renewal mechanism...

blazor.webassembly.js:1 crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
Unhandled exception rendering component: null_or_empty_id_token: The idToken is null or empty. Please review the trace to determine the root cause. Raw ID Token Value: undefined
ClientAuthError: null_or_empty_id_token: The idToken is null or empty. Please review the trace to determine the root cause. Raw ID Token Value: undefined