In SAS^® Studio Enterprise 3.6 and earlier releases, the setting for the user preference Time-out interval determines the length of inactivity that can occur before you are signed out of SAS Studio and all other web applications. For these releases, the Log user off on time-out middle-tier security policy setting is not used. 

In SAS^® Studio Enterprise 3.7, 3.71, and 3.8, when the SAS Studio Time-out interval preference is reached during a SAS Studio session, you are timed out of that session, but not signed out. (Being signed out means that you must reauthenticate your identity in order to open a new session.) The time-out occurs only in the session that reached the setting for inactivity, and you are not signed out of any other SAS Studio sessions or other web applications. You can start a new SAS Studio session without reentering credentials if you do so within the global single sign-on (SSO) time-out interval (the default is 12 hours). There is no way to force a sign-out of SAS Studio based on the Time-out interval preference.

If you want a user to be signed out of all web applications after a certain time interval, you can adjust the global SSO time-out interval setting. For more information about adjusting the global SSO time-out interval and the Log user off on time-out policy setting, see the SAS^® 9.4 Intelligence Platform: Middle-Tier Administration Guide.

Click the Hot Fix tab in this note to access the hot fix for this issue.

The hot fix enables SAS Studio to honor the Log user off on time-out policy setting in order to determine which web application sessions are affected, and whether you are signed out completely or not. 

When the policy setting is Yes, you are signed out of all SAS Studio sessions and all other web applications when the user preference Time-out interval is met during one SAS Studio session.

When the policy setting is No, you are timed out of an inactive SAS Studio session, but you can sign back in without reentering credentials if you are within the global SSO time-out interval. You are not signed out of other SAS Studio sessions or other web applications.

Operating System and Release Information

A fix for this issue for SAS Studio 3.8 is available at:

A fix for this issue for SAS Studio 3.71 is available at:

A fix for this issue for SAS Studio 3.7 is available at: