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
I’m implementing an OAuth-based API integration using Keycloak 26.
The idea: give partners a refresh token that they can use to get short-lived access tokens for backend calls.
I need each refresh token to have a custom (dynamic) expiry at creation time — not just the default realm or client lifespan.
Is there any supported way to set refresh token expiry dynamically (e.g. via token exchange or another flow), or should I implement a custom SPI to handle this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I’m implementing an OAuth-based API integration using Keycloak 26.
The idea: give partners a refresh token that they can use to get short-lived access tokens for backend calls.
I need each refresh token to have a custom (dynamic) expiry at creation time — not just the default realm or client lifespan.
Is there any supported way to set refresh token expiry dynamically (e.g. via token exchange or another flow), or should I implement a custom SPI to handle this?
What is the best practice?
Thanks
All reactions