<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
0D50Z00008G7VJfSANOkta Classic EngineOkta Integration NetworkAnswered2024-04-30T09:18:25.000Z2018-02-27T21:10:23.000Z2018-03-13T00:10:39.000Z
is it possible to base SAML session timeouts on user activity rather than a static time period?
For example, AWS:  users need long session times during business hours, but sessions should close when not in use.  We set the timeout to 4 hours, but many users work on sessions all day and get kicked out.

  • Hey Greg,

    In SAML, the Service Provider side is actually responsible for the Session's validity and the Session Lifespan. Okta as the IdP does not set this value. A slight exception to this, is as you pointed out in the AWS App integration, where we just pass the value for Session to the Service Provider (AWS in this case) via their API upon connection. AWS as the SP is still responsible for the Session and are in control of it's lifespan and validity.
    Expand Post
  • j5v7c (j5v7c)

    Hello,

     

    Thanks for posting your inquiry in Okta Community Portal.

     

    ​If you receive a great answer to your question(s), please help readers find it by marking it the best answer. Hover over the answer and click "Best Answer." 

     

    Thank you,

     

    ​Dylann Fezeu

    OHC Team
    Expand Post
This question is closed.
Loading
is it possible to base SAML session timeouts on user activity rather than a static time period?