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
Is it generally possible to cache an access token on a resource server, even if it may expire during that short period of continued usage, considering that there are no other resource servers involved and the token is only used for local operations such as database persistence?
I have to cache the Access Token for at least 5 minutes. At the same time, it is only valid for 30 minutes. If a user goes to the backend just before the access token expires (e.g. in minute 29), the invalid token is cached for another 4 minutes. So an invalid token will be used. For me it's okay because it's only some minutes. But is this any problem from a technical point of view?
Is it generally possible to cache an access token on a resource server, even if it may expire during that short period of continued usage, considering that there are no other resource servers involved and the token is only used for local operations such as database persistence?
I have to cache the Access Token for at least 5 minutes. At the same time, it is only valid for 30 minutes. If a user goes to the backend just before the access token expires (e.g. in minute 29), the invalid token is cached for another 4 minutes. So an invalid token will be used. For me it's okay because it's only some minutes. But is this any problem from a technical point of view?
This is my code:
The text was updated successfully, but these errors were encountered: