Skip Navigation

Search

SSO-enabled agents are still logged on upon reaching the idle time limit
Answer ID 8591   |   Last Review Date 04/27/2026

Why are our SSO-enabled agents still logged on upon reaching the idle time limit from the CLIENT_SESSION_EXP configuration setting?

Environment:

All Oracle B2C Service versions

Issue:

The SSO-enabled agents are still logged after their idle time limit has exceeded the value configured in the CLIENT_SESSION_EXP configuration setting.

Resolution:

In order to handle the automatic logout of SSO-enabled agents which are exceeding the idle time limit, please set up the following configuration setting: SSO_IDP_SSO_SESSION_EXP.

Description:
Specifies the number of minutes the client can remain idle until the user is forced to re-enter the credentials to continue. This values is applicable only for sessions created from Single Sign-On session. Setting the value to 0 disables this feature. Maximum is 1440 (24 hours). Default is 480.

Path to configuration:

Configuration --> Site Configuration --> Configuration Settings --> type the SSO_IDP_SSO_SESSION_EXP setting in the Key field and change the value according to your business need.

Configuration --> Site Configuration --> Configuration Settings --> type the SSO_IDP_SSO_SESSION_EXP setting in the Key field


For information on editing configurations, please see Answer ID 1960: Editing configuration settings. See also Answer ID 13084: Interview not Loading after SSO Idle Timeout

Note

In the account_session_history table, agents who are logged out due to this timeout event will have the Logout Reason recorded as Hard Time Exceeded. This applies only for Single Sign-On (SSO) session types. For Web Console and Agent Desktop session types,  the Hard Time Exceeded logout reason is recorded based on the value defined in the SESSION_HARD_TIMEOUT configuration setting. See also Answer ID 7945: Agent session locked even though he is logged in and active