<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
0D50Z00008C3jhpSABOkta Classic EngineSingle Sign-OnAnswered2024-04-20T03:26:20.000Z2017-10-16T19:55:42.000Z2017-10-17T15:24:25.000Z
Idle timeout and Maximum timeout setting for Application
Is there a way to configure Idle timeout and Maximum timeout for JAMF or any other application such that user is prompted to re-enter their credentials after the timeout setting?

 

I could see "Prompt for re-authentication" while creating a rule. Will that be a substitute to maximum timeout?

  • Hi Raja,

     

    Thank you for reaching out to Okta.

    The "Prompt for re-authentication" option applies when the user clicks on the application chiclet from the Okta Dashboard or when the user tries to access it from the login page. If the user is already on the application page, access to resources within will still be granted without re-authentication.   

    The "Session lifetime" configured under the Okta Security>>Authentication>>Sign-on, apply to the Okta session.

    The timeout for a JAMF will have to be set on the app side if it supports customisable session times.  

    I recomend reaching out to their support as well.

    Expand Post
This question is closed.
Loading
Idle timeout and Maximum timeout setting for Application