<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
0D51Y00008pcAC6SAMOkta Classic EngineSingle Sign-OnAnswered2024-03-25T10:36:23.000Z2020-06-29T10:29:24.000Z2020-07-06T20:48:31.000Z
  • Thank you so much for reaching out to Okta Support

     

    For some time now, Okta has stripped the relayState values for authentication attempts (where to redirect after authentication) in favor of okta_key values. Basically, when a user accesses a page in Okta and does not have an active session, the path that he accessed in saved in our database, along with a token and that token is returned back to the user and added under okta_key variable. In our database, the lifetime of the okta_key is 15 minutes, meaning that, if the user authenticates after 15 minutes (after the okta_key expires), they will receive an error message because the key expired and then they will need to reauthenticate and access manually the previous path.

     

    The only current solution is to refresh the Okta-hosted login page, which will start a new session and users will be able to login.

     

    There is currently a feature request, that has been made and you can vote on to make this option available to update the timeout. If it gets enough votes, Engineering will review and work on implementation.

     

     https://ideas.okta.com/app/#/case/123743

     

    If you have any further concerns, please reach out to Support@okta.com and create a ticket. A Support Engineer will be able to assist. Thank you again! 

     

    Expand Post
This question is closed.
Loading
Need to update okta_key default expiry value which is 15 mins