Skip to main content
Question

IFSCloud timeout Setting Confirmation.


Forum|alt.badge.img+3

SSO integration with OpenIDConnect with IFSCloud and MicrosoftEntraID.
There are two login entry points.

Confirmation 1 
For SSO login, EntraID issues an access token, an ID token, a refresh token, and a session token. The validity period of each token is controlled by the EntraID settings. Are there any errors?

Confirmation 2 
For IFSCloud login, IFSCloud issues an access token, ID token, refresh token, and session token. The validity period of each token is determined by the IFSCloud settings: System parameter[Time a session is allowed to be idle before it expires][Max time before a session is expired] and Configuring IAM Sessions and Tokens[Access Token lifespan][Session Max][Sessions Idle]. Are there any errors?

Confirmation 3 
System parameter[Time a session is allowed to be idle before it expires][Max time before a session is expired] and Configuring IAM Sessions and Tokens[Session Max][Sessions Idle] are considered the same setting.

The System parameter is the default value; it can be overridden by the Configuring IAM Sessions and Tokens setting. Are there any errors?

0 replies

Forum|alt.badge.img+3
  • Author
  • Do Gooder (Partner)
  • 1 reply
  • June 18, 2025

The question was raised by the following statement in KB0065296

IFS Product - Not possible to alter the system parameter "Time a session is allowed to be idle before it expires"

 >SSO_SESSION_IDLE - Time a session is allowed to be idle before it expires.
 >SSO_SESSION_MAX - Max time before a session is expired.

[SSO_]?
The system parameter setting does not affect the EntraID_SSO linkage, right?

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings