<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
0D51Y00009hKmXPSA0Okta Classic EngineIntegrationsAnswered2024-04-16T10:43:23.000Z2020-10-13T13:14:26.000Z2020-10-21T07:37:18.000Z

wq4kj (wq4kj) asked a question.

User forced to login to Okta after browser was closed and opened again

When we logged in using Okta Single Sign On in our application (built on angular) and without log out if we close the browser and open again, system serves an okta login screen again.

Is there any way it maintains the logged in User session until user invokes logout mechanism ?


  • User15906048639596774956 (Vendor Management)

    Okta utilizes a 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. Session cookies have an expiration configurable by an administrator for the organization and are valid until the cookie expires or the user closes the session (logout) or browser application.

     

    refer - https://developer.okta.com/docs/reference/api/sessions/#session-cookie

    Expand Post
  • j5onj (j5onj)

    Hi Dragos,

     

    We have the same issue - our Session Token Lifetime is 3 months - cookies are not removed after we close the browser but we still need to log in again after 24 hours.

    What can we try to do to resolve this?

     

    Expand Post
This question is closed.
Loading
User forced to login to Okta after browser was closed and opened again