clientAuthError: token_refresh_required Issue after update to Vs 17.12.4

Question

clientAuthError: token_refresh_required Issue after update to Vs 17.12.4

Inam Siddiqui 20

I am getting error when trying to start project in debug mode in AthuenticationService.js

Its starts coming after I update my vs version to latest v17.12.4 and instal .net 9 sdk

ClientAuthError: token_refresh_required: Cannot return token from cache because it must be refreshed. This may be due to one of the following reasons: forceRefresh parameter is set to true, claims have been requested, there is no cached access token or it is expired.

Stef Janssens 10 Reputation points

2025-02-06T10:57:33.29+00:00

I got exactly the same issue, whenever I debug my blazor webassembly standalone project that uses msal, I get the Exception unhandled error: ClientAuthError: token_refresh_required: Cannot return token from cache because it must be refreshed. This may be due to one of the following reasons: forceRefresh parameter is set to true, claims have been requested, there is no cached access token or it is expired.

When i click continue, my app just runs fine.
Matej Hlavaj 0 Reputation points

2025-03-17T16:31:05.69+00:00

i have exactly same problem

1 answer

Your answer

Stef Janssens 10 Reputation points

2025-02-06T10:57:33.29+00:00

I got exactly the same issue, whenever I debug my blazor webassembly standalone project that uses msal, I get the Exception unhandled error: ClientAuthError: token_refresh_required: Cannot return token from cache because it must be refreshed. This may be due to one of the following reasons: forceRefresh parameter is set to true, claims have been requested, there is no cached access token or it is expired.

When i click continue, my app just runs fine.
Matej Hlavaj 0 Reputation points

2025-03-17T16:31:05.69+00:00

i have exactly same problem

Answer 1

Orlando Villa 5

Solved this issue by adding all the required scopes to the DefaultAccessTokenScopes when adding the msal authentication service.

Seems that it prevents the client from requesting a new token due to missing scopes in the existing/cached token.

Orlando Villa 5 Reputation points

2025-02-17T05:30:02.88+00:00

I am having the same issue, which persists after upgrading to VS 17.13.0. Uncertain if the issue is related to visual studio or MSAL.

Mog0 0

This has fixed the most annoying glitch I've been struggling with for months.

For others struggling to find DefaultAccessTokenScopes, my MSAL config is:

builder.Services.AddMsalAuthentication<RemoteAuthenticationState, CustomUserAccount>(options =>
{
    builder.Configuration.Bind("AzureAd", options.ProviderOptions.Authentication);
    options.UserOptions.RoleClaim = "appRole";
    options.ProviderOptions.DefaultAccessTokenScopes.Add(builder.Configuration["DownstreamApi:Scopes"] ?? throw new InvalidOperationException("No Scopes"));
})
.AddAccountClaimsPrincipalFactory<RemoteAuthenticationState, CustomUserAccount, CustomAccountFactory>();

Matej Hlavaj 0 Reputation points

2025-03-17T16:32:50.1333333+00:00
I cannot give there all the scopes as i have multiple scope sources (azure api and grpahql)
...

options.ProviderOptions.DefaultAccessTokenScopes.Add("api://client_id/Scopes.Read");

then i have :
public class GraphAuthorizationMessageHandler : AuthorizationMessageHandler

{

public GraphAuthorizationMessageHandler(IAccessTokenProvider provider, NavigationManager navigationManager) : base(provider, navigationManager) { ConfigureHandler( authorizedUrls: new[] { "https://graph.microsoft.com/" }, scopes: new[] { "User.Read.All", "User.ReadBasic.All", "User.Read.All" }); } ```}

Share via

clientAuthError: token_refresh_required Issue after update to Vs 17.12.4

1 answer

Your answer