Click HERE to see how Saviynt Intelligence is transforming the industry. |
09/05/2024 10:49 AM
Hi Team,
Is it feasible in Saviynt to extend the expiry time for the refresh token. Currently in the response payload we could see the token is valid for 3600 seconds. We have a requirement to have the token valid for 6 months.
09/05/2024 11:09 AM
No. Its not configurable Please raise idea ticket with business use case
09/05/2024 11:12 AM
@Debankita
You can extend connection time out but not Refresh token.
09/05/2024 01:03 PM - edited 09/05/2024 01:07 PM
Earlier Saviynt docs used to have below "note" information. We increased the lifetime of token using config.groovy in old versions.
Note: If grails.plugin.springsecurity.rest.refreshtoken.storage.jwt.expiration is set to some value in Config.groovy, refresh token will expire based on this config in api/login api. This will generate a new refresh token if another config - grails.plugin.springsecurity.rest.refreshtoken.new is set to true in Config.groovy. For blank or null, it will return the same Refresh token as passed in oauth/access_token api
I don't see it now but I believe if you reach out to Saviynt. They can let you know if config.groovy can be updated internally to meet your expectations.
If not possible in EIC, there is an enhancement already for this - https://ideas.saviynt.com/ideas/EIC-I-4932