<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00006sRoS8CAKOkta Classic EngineIntegrationsAnswered2024-08-29T09:01:02.000Z2021-03-15T22:13:04.000Z2021-03-17T13:25:25.000Z

w48a7 (w48a7) asked a question.

Why is id token lifetime/expiration not configurable?

It's been asked previously whether it is possible to extend or configure the expiration for the id token that an Okta authentication server generates:

 

 

And Okta employees of dutifully regurgitated the documentation stating that it is hard coded to 1 hour (https://developer.okta.com/docs/reference/api/oidc/*token-lifetime). But nobody has bother to explain why it is like this?! Or how one is suppose to create a application using Okta for authentication that doesn't have either a completely abysmal user experience of forcing the user to re-authenticate every hour, or resort to some sort hack like ignore JWT expiration and checking the Issued At timestamp instead. If there is some documentation on how to get a refreshed id token without harassing my user that would be helpful, however that's kind of a crap solution since it's just making extra work for me when you ought to just be letting me configure Id Token expiration like I can configure Access Token expiration.


This question is closed.
Loading
Why is id token lifetime/expiration not configurable?