How to deal with stale tokens - Is there a way to update the Access Token TTL?

[tonyjmnz-ss]

I'm dealing with a situation that probably a lot of people have run into, but I'm not having luck finding the right settings in Logto

Essentially, changes to the Logto user record (e.g: adding or removing roles) could make the user's JWT stale. I've found 2 solutions to this problem

1. Lower the Access Token TTL to ~5mins (default is 1h). This would mean that a user's token would go stale for at most 5 minutes and then it'll be refreshed with the most recent data. I like this approach - however, I can't find a setting in the console UI to update this
2. On BE apps, don't trust the roles that are present in the token and instead validate against the Logto server. This would solve it but it beats the purpose of having the roles set in the JWT token if they can't be trusted.

Has anyone solved this issue before?

[xiaoyijun]

Hi @tonyjmnz-ss , this is how Logto cloud deal with the stale token, FYI: https://blog.logto.io/implement-user-collaboration-in-your-app#handle-scope-updates-in-access-tokens

[tonyjmnz-ss]

Thanks for the reply, unfortunately I'm not using Logto Cloud and the solution, while robust, seems complex

Is there a way to modify the access token TTL in the FOSS version?