# 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:** 1\
**Showing post:** 17

<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)?

---

_[View the full topic](https://community.auth0.com/t/auth0-aspnetcore-authentication-userrefreshtoken-true-is-not-refreshing-tokens-in-blazor-server/182843)._
