You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note
The access token function you provide is called before every HTTP request made by SignalR. If you need to renew the token in order to keep the connection active (because it may expire during the connection), do so from within this function and return the updated token.
Can this be elaborated on a little? How does the client know if the token needs to be renewed?
Do I need to ping a URL first to check if the token has expired and then if I get a 401, then send the refresh token to get a new auth token?
Is there any existing guidance / best practice for this?
Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core which hasn't been addressed, please file a new issue.
Can this be elaborated on a little? How does the client know if the token needs to be renewed?
Do I need to ping a URL first to check if the token has expired and then if I get a 401, then send the refresh token to get a new auth token?
Is there any existing guidance / best practice for this?
These seem related:
dotnet/aspnetcore#5283
dotnet/aspnetcore#5297
dotnet/aspnetcore#14578
Thanks.
Edit:
Seems I overlooked the JWT can be parsed on the client to check the expiry.
Presume that's how to do this?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: