# Auth0-aspnetcore-authentication "UserRefreshToken = true;" is not refreshing tokens in Blazor Server

**URL:** <https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843>\
**Category:** Dev to Dev Hub\
**Tags:** rotating-refresh-tokens, sessions\
**Created:** [February 25, 2025, 6:11pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843 "2025-02-25T18:11:59Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [February 25, 2025, 6:11pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/1 "2025-02-25T18:11:59Z")

</div>

Here is the _ **TL;DR** _ version: When adding the setting `UserRefreshToken = true;` to `Program.cs` (see the larger code snippet at the bottom of this page for more detail), what exactly is the behavior supposed to be within an AspNetCore based application? Automatic refresh does not appear to be the case in a Blazor Server application.

* * *
... okay moving back to the way TL stuff... 

Posted similar question/comments on [a closed issue](https://github.com/auth0/auth0-aspnetcore-authentication/issues/66) for the `auth0-aspnetcore-authentication` sdk focusing on the follow:

> The refresh token does not automatically refresh correctly when using `UseRefreshTokens = true`.

This issue has been long closed after the reporter submitted as PR and it was accepted and merged (April 2022).

However, the token’s lack of being refreshed is still my experiences in the context of a Blazor Server application. I am leaning heavily into this is a “I’m doing it wrong” and/or “I misunderstand how this works” rather than this is a bug that needs to be fixed within the `Auth0-AspNetCore-Authentication` sdk.

Let me add context, I have tried to simplify what I am doing by using the [Blazor Sample App](https://github.com/auth0-samples/auth0-aspnetcore-blazor-server-samples/tree/main), and still no refreshing of tokens occurs.

Maybe my expectations are wrong… Using the sample app, and with the Auth0 Tenant Application settings, I am setting my application Id Token Expiration to a low value, say 60 seconds, and the Refresh Token Expiration to similar value, the token’s never refresh. I see the same JWT and refresh token after the expiration date on the `/Profile` page (edited to show all Id, Access, and Refresh tokens). I would expect that while using the app, it would automatically refresh the token at some point, and if I’m idle, I would expect the app to force me to reauthenticate if I try to access the site, or navigate around, beyond those expiration times.

I have also setup an API in Auth0 to be able to add in an Audience in the Program.cs setup, and to set a shorter Access Token as I wondered if somehow the Access Token’s expiration time would come into play. That seems to have no affect, other the providing another expiry time in a token.

I have noticed, that once I surpass the `Maximum Refresh Token Lifetime` as set in Auth0, a hard refresh of the `Profile` page in the sample app continues to give me the original ID and Access tokens, but now the refresh token is blank…

I am assuming, at this point, that I am misunderstanding what the SDK is supposed to do when adding the line `options.UseRefreshTokens = true;` to the `Program.cs` setup. This [blog post](https://auth0.com/blog/use-refresh-tokens-in-aspnet-core-apps/) also seems to indicate that the line should provide some sort of automation of the refresh process. I and thinking what needs to occur is an integration of the `Auth0.AuthenticationApi` SDK and manually setup the token refresh if there is activity and the token is nearing expiration. If that is the case, then it seems I should reduce dependencies and roll a more custom implementation with the Authentication API for login, logout, and token management.

Anyway, what is this line supposed to actually do within the Blazor Server Sample App, or a Blazor Server app in general? Perhaps the lack of a more dedicated .net core based API does not initialize the automated code within this sdk?

```auto
...
builder.Services.AddAuth0WebAppAuthentication(options =>
{
    options.Domain = builder.Configuration["Auth0:Domain"];
    options.ClientId = builder.Configuration["Auth0:ClientId"];
    options.ClientSecret = builder.Configuration["Auth0:ClientSecret"];
    options.Scope = "openid profile email";
}).WithAccessToken(options =>
{
    options.Audience = builder.Configuration["Auth0:Domain"];
    options.UseRefreshTokens = true; <--- This is supposed to do what, beyond giving me a refresh token?
});

```

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [February 26, 2025, 10:25pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/3 "2025-02-26T22:25:24Z")

</div>

Hi @jeffcodes

I would recommend you to review the following article regarding securing Blazor Apps:

- [How to Secure Blazor WASM Applications with Auth0](https://auth0.com/blog/securing-blazor-webassembly-apps/)

You might be missing this piece of code inside the `Client` folder in the `Program.cs` file:

```auto
builder.Services.AddOidcAuthentication(options =>
{
  builder.Configuration.Bind("Auth0", options.ProviderOptions);
  options.ProviderOptions.ResponseType = "code";
});

```

You can also check if you are not using the [Implicit Flow](https://auth0.com/docs/authenticate/login/oidc-conformant-authentication/oidc-adoption-implicit-flow) since that does not support refresh tokens.

Let me know if this solves the issue or if you have any other questions!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [February 27, 2025, 1:46pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/4 "2025-02-27T13:46:29Z")

</div>

I’ll read through this again. We have a Blazor Server app, not web assembly, so some of the scaffolding here is different.  
Will read up on the implicit flow stuff as well. Thanks.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [February 28, 2025, 4:01pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/5 "2025-02-28T16:01:20Z")

</div>

Hi @jeffcodes

Sorry for the late reply! I will keep investigating the matter regarding refresh tokens for the Blazor Server, as far as I have investigated, the `UserRefreshToken = true` should do the trick for most .NET or Blazor applications, regardless of them being web apps or servers, I presume it might be a matter of the application not being considered secured and that is why the refresh tokens do not rotate or are not visible.

I will post some useful info as soon as possible regarding the matter, if you have updates of your own, please feel free to post them here if necessary!

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [February 28, 2025, 5:00pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/6 "2025-02-28T17:00:31Z")

</div>

I do appreciate it. I had to switch to some other stuff, but will come back to this. Honestly, I have a gut suspicion it is in my setup. The only thing that makes me even question that is that I cannot get it to work with the sample app from Auth0 either.

If I come up with anything, I will certainly come back with that information here.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [February 28, 2025, 6:58pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/7 "2025-02-28T18:58:43Z")

</div>

Hi again.

I found some possible references to the matter, I am not quite sure if you have reviewed these yet:

- [GitHub - akhanalcs/blazor-api-auth0: Sign in users and call a protected API from a Blazor Server app.](https://github.com/akhanalcs/blazor-api-auth0)
- [Use Refresh Tokens in ASP.NET Core Apps](https://auth0.com/blog/use-refresh-tokens-in-aspnet-core-apps/#Set-up-the-Sample-Application)
- [auth0-aspnetcore-authentication/EXAMPLES.md at main · auth0/auth0-aspnetcore-authentication · GitHub](https://github.com/auth0/auth0-aspnetcore-authentication/blob/main/EXAMPLES.md#refresh-tokens)
- [auth0-aspnetcore-authentication/EXAMPLES.md at main · auth0/auth0-aspnetcore-authentication · GitHub](https://github.com/auth0/auth0-aspnetcore-authentication/blob/main/EXAMPLES.md#register-the-sdk)

You mentioned about trying out our sample app and refresh tokens did not work there either, was the sample app the one references above by any chance?

Also, I noticed that for your `options.Audience` you seem to be passing `Auth0:Domain`. I am not 100% familiar with .NET or Blazor applications, however, I believe it should be something like ` options.Audience = Configuration["Auth0:Audience"];` as mentioned in this [community post](https://community.auth0.com/t/add-auth0-authentication-to-blazor-web-apps/125476/20).

Also, are you using a custom API by any chance and are you passing in the correct audience inside your implementation?

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [February 28, 2025, 7:37pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/8 "2025-02-28T19:37:34Z")

</div>

Thank you, again, so much. I will review when I get a chance.  
I was passing in the Audience. Passing in the domain was a suggestion from someone else I just tried before posting. Good catch.

---

<div class="post-metadata">

**Author:** ![andrea.chiarelli](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/andrea.chiarelli/32/16034_2.png) [@andrea.chiarelli](https://community.auth0.com/u/andrea.chiarelli)\
**Post date:** [March 7, 2025, 11:55am UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/9 "2025-03-07T11:55:12Z")

</div>

Hey @jeffcodes,  
I’m not sure if you solved your problem with refresh tokens.  
Just wanted to confirm that Blazor Server apps are ASP.NET Core applications, and the instructions in [this article](https://auth0.com/blog/use-refresh-tokens-in-aspnet-core-apps) still apply.

Take a look at the sub-section “_Adjust the token expiration tolerance_” in that article. You may experience some delay in your development environment due to the token expiration calculation.

I hope this helps.

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [March 7, 2025, 2:06pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/10 "2025-03-07T14:06:52Z")

</div>

@nik.baleca

Thanks for all the help, both of you. I have gone through all things provided by you two within our application, and most of it within the sample Blazor App provided by Auth0, and none of these result in the token being refreshed. I am able to receive the refresh token; however, nothing I have tried leads to refreshing the ID or Auth tokens.

@andrea.chiarelli, I have gone through your article a number of times you linked as well. We are hitting a PowerBI API, and a local database through a service layer that I can set-up to look like an API, so I can follow your steps more closely to get the token refreshed; however, I am still unable to get a refresh.

At this point, I have abandoned trying to further integrate a more automated solution using Auth0 and have written a custom solution do some of the work that this was intended to do as we are facing a deadline that cannot be moved.

The documentation you write, @andrea.chiarelli, has helped me with a number of things, and Auth0’s documentation overall has been great. I do appreciate the help. There is clearly something within my implementation or understanding that prevents me from making this all work.

It would be great if Auth0 could provide a fully fledged Blazor Server sample app that you know works for sure simply by uncommenting some code in the `Program.cs` file to use the Refresh tokens, and entering in the ID’s and values form a users Auth0 tenant in the `appsetting.json` file. If the instructions you have listed are as simple as you have written, then it seems like it would be a pretty simple addition to your [Blazor Sample App](https://github.com/auth0-samples/auth0-aspnetcore-blazor-server-samples/tree/main), noted above.

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [March 7, 2025, 4:27pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/11 "2025-03-07T16:27:50Z")

</div>

I am also having this issue with my Blazor Server application. My server app hits an API that is hosting a hub connection used for chatting with users of another application. In my program.cs I have a call to `.WithAccessToken` and set the `options.UseRefreshTokens = true` in the setup.

@andrea.chiarelli I followed the document you linked, ensuring I had everything enabled on the Auth0 side.

The issue that is occurring is that the API token is expiring and is not refreshing once expired. The only way to get a new token, it seems, is to log out or clear the security cookie. So given the TTL on the auth for the server app, the user comes back and is not required to sign in. The associated access\_token is pulled from claims when initializing the hub connection and has expired.

So I guess the question is, what is the mechanism that triggers the refreshing of the API access token? Is it part of the OIDC backchannel communications that occur, or does there need to be some kind of event handler/token provider put in place to call the Auth0 API to obtain a new token?

---

<div class="post-metadata">

**Author:** ![andrea.chiarelli](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/andrea.chiarelli/32/16034_2.png) [@andrea.chiarelli](https://community.auth0.com/u/andrea.chiarelli)\
**Post date:** [March 13, 2025, 5:27pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/12 "2025-03-13T17:27:11Z")

</div>

@jdbahnick, @nik.baleca,  
Using the `UseRefreshTokens = true` option enables automatic renew of an access tokens from the authorization server. No other code is required on your side to renew the access token. If you want to see the details of how it works, take a look [here](https://github.com/auth0/auth0-aspnetcore-authentication/blob/370ba0ae595f4e9ab876d6b8b9ee0892d60f2eec/src/Auth0.AspNetCore.Authentication/AuthenticationBuilderExtensions.cs#L183).

This only works if your API is configured to [allow offline access](https://auth0.com/docs/get-started/apis/api-settings#access-settings), of course.

There may be edge situations where the token renewal does not work automatically. In these cases, you can use [this approach](https://github.com/auth0/auth0-aspnetcore-authentication/blob/main/EXAMPLES.md#detecting-the-absense-of-a-refresh-token). However, in normal situations it should work as expected.

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [March 17, 2025, 1:31pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/13 "2025-03-17T13:31:21Z")

</div>

I confirmed both requirements for refresh tokens and confirmed that offline\_access is part of the request scope. It seems then that I’ll have to complete the manual approach in order to refresh the token.

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [March 18, 2025, 2:59pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/14 "2025-03-18T14:59:26Z")

</div>

I did the same, confirmed the offline\_access was set, and part of require scope. Still could not get this work.

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [March 20, 2025, 7:53pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/15 "2025-03-20T19:53:04Z")

</div>

I wonder if this has something to do with the issue: [Refresh token during http…](https://github.com/dotnet/aspnetcore/issues/55213).

I assume that .NET is storing the access-token in a cookie. However, if that cookie expires the same time as the Id token. I’m thinking that I’ll have to implement an OIDC Cookie Refresher to handle the refreshing of the API token.

EDIT:  
So I think I found my issue. Since my token is being used for the hub connection that is hosted by an API, I missed the note in the documentation about needing to manually refresh the access token since SignalR does not provide implicit management.

[Bearer token authentication](https://learn.microsoft.com/en-us/aspnet/core/signalr/authn-and-authz?view=aspnetcore-9.0#bearer-token-authentication)

> The access token function provided is called before **every** HTTP request made by SignalR. If the token needs to be renewed in order to keep the connection active, do so from within this function and return the updated token. The token may need to be renewed so it doesn’t expire during the connection.

So for me, I’ll just need to create a class to help access and manage the token for my hub connection and push that token into the Identity.

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [March 25, 2025, 8:00pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/16 "2025-03-25T20:00:02Z")

</div>

@andrea.chiarelli I have a follow-up question now… (feel free to have me ask a new questions)

When my access token for my API expires, I implemented code to call to the `/oauth/token` endpoint passing in the client Id and secret for the blazor server app, and the refresh token obtained during login. If my API access token is currently valid, this request returns a new access token, id token, and refresh token. However, if the api access token has expired, calling to the token endpoint with a valid refresh token returns a 403.

So my question is, what am I missing? I thought the purpose of the refresh token was to obtain a new access token. Why does the refresh token only work when the API access token is still valid?

---

<div class="post-metadata">

**Author:** ![andrea.chiarelli](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/andrea.chiarelli/32/16034_2.png) [@andrea.chiarelli](https://community.auth0.com/u/andrea.chiarelli)\
**Post date:** [March 31, 2025, 8:47am UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/17 "2025-03-31T08:47:27Z")

</div>

Hey @jdbahnick,  
Refresh tokens should be working as you expect, unless there are other reasons for that `403` response. Take a look [here](https://community.auth0.com/t/403-forbidden-error-when-renewing-token/93187/9) and [here](https://community.auth0.com/t/refresh-token-unknown-or-invalid-before-expiry-403-unknown-or-invalid-refresh-token/120406) for possible causes.

However, my question is, why are you implementing the refresh token flow manually for your Blazor server app instead of relying on the [Auth0 ASP.NET Core Authentication SDK](https://github.com/auth0/auth0-aspnetcore-authentication)?

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [March 31, 2025, 4:09pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/18 "2025-03-31T16:09:16Z")

</div>

@andrea.chiarelli The access token is used for the API that is hosting the hub connection for a chat client, which is not in a shared domain. Per .NET documentation, hub connections do not refresh access tokens and the logic for doing so must be provided.

I believe this is my issue here:

> [@Refresh Token Unknown or Invalid before expiry "403: Unknown or invalid refresh token"](https://community.auth0.com/t/refresh-token-unknown-or-invalid-before-expiry-403-unknown-or-invalid-refresh-token/120406/1):
>
> **(2) Custom Logics**  
> A customer has a custom logic that handles refresh tokens outside of our SDK.  
> The SDK handled the login flow and saved the first refresh token. This refresh token was reused and rotated somewhere else without letting the SDK know that. As a result, the SDK reused the first refresh token, and all the following family tokens were invalidated.

I confirmed in the Auth0 logs that the access token is being refreshed automatically.

So my question now is, how do I properly get to the access token? A hub connection requires a delegate that returns a string (access token). What can I tap into so that I can detect when a refresh occurs so I can keep the access token for my hub connection up to date? I tried adding an event handler to `AuthenticationStateProvider.AuthenticationStateChanged`, but it appears that this is not firing for token refreshes.

---

<div class="post-metadata">

**Author:** ![jdbahnick](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jdbahnick/32/58402_2.png) [@jdbahnick](https://community.auth0.com/u/jdbahnick)\
**Post date:** [April 1, 2025, 3:51pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/19 "2025-04-01T15:51:55Z")

</div>

Here are some Github issues in regards to Blazor server and API refresh tokens:

[Logged in 2024](https://github.com/dotnet/aspnetcore/issues/55213)  
[Logged in 2019](https://github.com/dotnet/aspnetcore/issues/8175)

To solve my issue, I implemented a cookie refresher, with some modifications I needed:  
[OidcCookieRefresher](https://github.com/dotnet/blazor-samples/blob/main/8.0/BlazorWebAppOidc/BlazorWebAppOidc/CookieOidcRefresher.cs)

Setting up the refresher in `Program.cs`:

```auto
    builder.Services.AddSingleton<CookieOidcRefresher>();
    builder.Services.AddOptions<CookieAuthenticationOptions>(CookieAuthenticationDefaults.AuthenticationScheme)
        .Configure<CookieOidcRefresher>((cookieOptions, refresher) =>
        {
            cookieOptions.Events.OnValidatePrincipal = context => refresher.ValidateOrRefreshCookieAsync(context, "Auth0");
        });

```

@jeffcodes Hopefully this will assist you with your issues as well.

---

<div class="post-metadata">

**Author:** ![jeffcodes](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jeffcodes/32/60175_2.png) [@jeffcodes](https://community.auth0.com/u/jeffcodes)\
**Post date:** [April 4, 2025, 2:08pm UTC](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843/20 "2025-04-04T14:08:30Z")

</div>

> [@jdbahnick](#):
>
> refresh the access token since SignalR does not provide implicit management.

Thank you @jdbahnick, I am no longer on the project where this concern was; however, I will make sure to pass on the information.