<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
0D51Y00005uaZlMSAUOkta Classic EngineSingle Sign-OnAnswered2024-04-15T10:28:10.000Z2019-01-24T19:18:28.000Z2019-01-25T02:57:17.000Z
  • GabrielL.85945 (Customer)

    This behavior is likely on the OneDrive side. Okta just does the authentication. The remaining behavior is typically determined on the OneDrive side.

     

    If accessed through a browser, there are two sessions: a session for Okta and a session for OneDrive. If the session for OneDrive ends, you'll need to authenticate with Okta again to create a new session for OneDrive. If you're not logged into Okta already, you'll likely be prompted for credentials from Okta again. If you do have an active session with Okta, then you'll probably be automatically authenticated and SSO into OneDrive.

     

    If this is from a rich-client, then Okta likely has no involvement in the session time and is just fulfilling authentication requests.

     

    In summary, check what the session time is for OneDrive.

     

    But if you do need to check or change the session time for Okta, then go to your admin console and head over to Security > Authentication > Sign On, click the pencil icon to edit a rule, and there will be a configuration item for "Session expires after".

    Expand Post
This question is closed.
Loading
Okta timeout settings