Hello Martin

Good afternoon 

Thank you for contacting us to clarify your doubts and help you with the setup of your deployment 

You can verify and modify the session lifetime for the Sign-on Policy if needed, you just need to click on Security -> Authentication -> Sign-On -> check or add the New Okta Sign-on Policy on top of the default one. There you can verify if the session lifetime is lower than the expected, you can change it to up to a maximum of 90 days.

 if you want to know more about this topic you can use the link below as a reference:

https://help.okta.com/en/prod/Content/Topics/Security/healthinsight/session-lifetime.htm

Let us know if this article helps you or if you have any other inquiries. 

Have a great day ahead 

Regards 

Henry Esquivel 

Okta.Inc 

Hello Anderson

Good afternoon 

That is correct, this can occur due to different reasons, as you can see below:

Session cookie 

Okta uses an HTTP session cookie to provide access to your Okta organization and applications across web requests for an interactive user agent such as a web browser. A session cookie has an expiration configurable by an administrator for the organization and is valid until the cookie expires or the user closes the session (logout) or browser application. You can verify this information using the link below:

https://developer.okta.com/docs/reference/api/sessions/ 

Sign-on Policy

Use this drop-down menu to specify the maximum idle time before an authentication prompt is triggered. The maximum allowed time for this option is 90 days. This is not the total connect time. The default session lifetime is 2 hours. This is idle time before users see a countdown timer at the 5-minute mark of the remaining session time. You can verify this information using the link below:

https://help.okta.com/en/prod/Content/Topics/Security/policies/configure-signon-policies.htm 

Session management

An Identity Provider (IdP) is a service that stores and manages digital identities. Okta is an IdP service that stores and verifies user identities. Okta provides a federated sign-in service so that a user can access multiple applications with a single set of sign-in credentials. A session is a group of user interactions with a resource, such as an IdP service or an application (app), for a given amount of time. When you use Okta as your IdP, there are two types of sessions that you need to consider for managing the user experience—the IdP session and the application session. You can verify this information using the link below:

https://developer.okta.com/docs/concepts/session/ 

Let us know if this article helps you or if you have any other inquiries. 

Have a great day ahead 

Regards 

Henry Esquivel 

Okta.Inc