Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Saviynt API - Refresh token expiry after every use

flegare
Regular Contributor III
Regular Contributor III

We have a customer who would like the refreshToken generated to expire after every use, as specified in the latest Security Best Current Practice.

Is this achievable in Saviynt using the available configuration process?

5 REPLIES 5

rushikeshvartak
All-Star
All-Star

This is accepted as enhancement 

https://ideas.saviynt.com/ideas/EIC-I-4932


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

AmitM
Valued Contributor
Valued Contributor

HI @flegare , It is supported but we/clients don't have access to make changes to the configurations.

We raised a ticket with Saviynt to get it updated. 

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

Thanks ,

Amit 

If this answers your query, Please ACCEPT SOLUTION and give KUDOS.

flegare
Regular Contributor III
Regular Contributor III

Hi @AmitM ,

This Config.groovy has nothing do to with the AuthenticationConfig.groovy file that we can maintain ourselves then, is it correct?

AmitM
Valued Contributor
Valued Contributor

Correct both are different.

Thanks,

Amit

flegare
Regular Contributor III
Regular Contributor III

If one was prone to sarcasm outbursts, one would ask why they feel the need to document this bit of information in the public api reference.

Thankfully, I am not that kind of individual.  Would go nuts real quick otherwise.

Thanks for the quick reply, much, much appreciated!