Skip to main content

If "IAM Session and Tokens Configuration" "Sessions" and "Session Idle" of IFSCloud are changed to "62Minutes" and "Session Max" to "64Minutes" 

 

logging in from 1, "Session Idle" is "62Minutes" and "Session Max" is "64Minutes" for logging in from 1, but they are not relevant for logging in from 2. Is the recognition correct?


In the article "KB0065296", the following is described as "SSO_" as in "SSO_SESSION", but I would like to confirm that it has nothing to do with logging in from 2.

 

"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.

 

Hi ​@KeyYasusW 

>logging in from 1, "Session Idle" is "62Minutes" and "Session Max" is "64Minutes" for logging in from 1, >but they are not relevant for logging in from 2. Is the recognition correct?

I'm not sure if you've tested it, but I believe this setting applies to all logged-in users.

After 24R2, you can change the parameter on this page.

 

Therefore, I believe the conclusion is that the system parameter setting affects all users, including those logged in via SSO.


Best regards,

Feng

Hi ​@feng 

 

We are currently testing 24R2 in out TEST environment where the “Time a session is allowed to be idle before it expires” has changed from 7200 (which our Production environment is set to)  to 1800.

 

Above you mention that this will be editable on this page after 24R2. We are on 24R2 UPD7 in our test environment. Is an update on this system parameter feasible on this page on this version? Is there another method to change it?

 

Thanks

Jason

Hi ​@jason.phillips1971 

You can use this page to change it.

 

Best regards,

Feng

Terms & ConditionsCookie settingsAccessibility statement