Repository navigation
Replies: 2 comments 3 replies
|
I am also facing same issue in v26.1.1 |
0 replies
|
@saadz24 |
3 replies
|
I have multiple applications under one realm. I actually need to adjust the token time only for one client out of many, not for the whole realm. |
|
@saadz24 so did you edit the SSO settings or just the access token stuff? |
|
The SSO settings as you mentioned gets applied across all clients. The client only settings work for max of 10 hours as mentioned in the issue description. Trying to figure out why it's capped to 10hours for a client. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have multiple clients under one realm. I need to configure a client with token lifespan and expiry of 30 days. I notice the "expires_in" param in the token response body shows 36000 (10 hours).
This value changes only when configured less than or equal to 10 hours anything more always returns as 10 hours.
Below are my configurations for reference.
Is there any max limitation to the token lifespan ? Because the dropdown provides option for days as well
All reactions