# Why is id token expiration not configurable? **URL:** \ **Category:** Questions\ **Created:** [March 16, 2021, 7:44pm UTC](https://devforum.okta.com/t/why-is-id-token-expiration-not-configurable/13384 "2021-03-16T19:44:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![paul\_sourcedrive](https://avatars.discourse-cdn.com/v4/letter/p/4af34b/32.png) [@paul\_sourcedrive](https://devforum.okta.com/u/paul_sourcedrive)\ **Post date:** [March 16, 2021, 7:44pm UTC](https://devforum.okta.com/t/why-is-id-token-expiration-not-configurable/13384/1 "2021-03-16T19:44:06Z")
I was told I should ask this here instead of [support.okta.com](http://support.okta.com) **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 a custom Okta authentication server generates: - help/s/question/0D50Z00008G7UgwSAF/how-to-change-id-tokens-lifetime - help/s/question/0D51Y00005lGBR2/is-it-possible-to-set-the-idtoken-lifetime-length And Okta employees have dutifully regurgitated the documentation stating that it is **hard coded** to 1 hour ([OpenID Connect & OAuth 2.0 API | Okta Developer](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. ¹ Since I was pointed to this forum I found an answer indicating that it is possible to create a webhook that is called at login time to set the expiration ([Token Inline Hook Reference | Okta Developer](https://developer.okta.com/docs/reference/token-hook/#sample-response-to-modify-token-lifetime)), but that seems like a lot of complexity just to set the expiration when it is already configurable for access tokens. If you have this issue please upvote: [https://ideas.okta.com/app/#/case/116706?section=requests](https://ideas.okta.com/app/#/case/116706?section=requests) So is there some rationale I’m missing? Is Okta planning on fixing this? ---
**Author:** ![eltronix](https://avatars.discourse-cdn.com/v4/letter/e/3ec8ea/32.png) [@eltronix](https://devforum.okta.com/u/eltronix)\ **Post date:** [March 17, 2021, 1:20pm UTC](https://devforum.okta.com/t/why-is-id-token-expiration-not-configurable/13384/2 "2021-03-17T13:20:22Z")
Okta this looks bad, after so many years of requests. ---
**Author:** ![amcneilly](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@amcneilly](https://devforum.okta.com/u/amcneilly)\ **Post date:** [November 24, 2021, 7:57am UTC](https://devforum.okta.com/t/why-is-id-token-expiration-not-configurable/13384/3 "2021-11-24T07:57:23Z")
> [@paul\_sourcedrive](#): > > the Issued At timestamp instead. If there is some documentation on how It is incredibly disappointing to see this question ignored by Okta. I am disappointed by the lack of complete functionality, poor documentation. how is this acceptable given the price charged. I will be changing to another product. I leave Okta frustrated and disappointed. You can do allot better! ---
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [February 12, 2024, 6:01pm UTC](https://devforum.okta.com/t/why-is-id-token-expiration-not-configurable/13384/4 "2024-02-12T18:01:54Z")
Closed on February 12, 2024, 6:01pm UTC