After upgrading to Cloud 25R1 our user sessions are timing out much more frequently even after extending the times on the Sessions and Tokens page.
We use SSO and the user is taken to an Azure Login Screen but this has happened on accounts that are not using SSO as well.
Some users have reported being logged out while they are working in the system and others after only working outside of IFS for only 5 - 10 minutes.
Has anyone else experienced this?
+3Hi,
We are also on 25R1 SU4 and experience these issues, where production employees are logged off when busy on production for a time between 6 - 10 minutes. Then need to logon again. The above suggestion to increase ‘Session Idle’ value is not possbile in 25R1 SU 4 (Cloud). Both menus [IAM Sessions and Tokens Configuration] and [IAM Client Details] show a “Access Token Lifespan” of 3 minutes and a “Session Idle” of 30 minutes. But this is actually much shorter. As we cannot edit any setup screen, anybody suggestion what to do for 25R1 SU4 CLOUD?
+5Hi all,
we have the same problem after upgrade to 25R1.
Do you already have a solution or information about this?
+5Hi
We applied the following settings which helped:
Regards,
Kajetan
+1Hi,
We are also on 25R1 SU4 and experience these issues, where production employees are logged off when busy on production for a time between 6 - 10 minutes. Then need to logon again. The above suggestion to increase ‘Session Idle’ value is not possbile in 25R1 SU 4 (Cloud). Both menus [IAM Sessions and Tokens Configuration] and [IAM Client Details] show a “Access Token Lifespan” of 3 minutes and a “Session Idle” of 30 minutes. But this is actually much shorter. As we cannot edit any setup screen, anybody suggestion what to do for 25R1 SU4 CLOUD?
You need AUTH ADMINISTRATOR access in System Priviliges to edit this values
After upgrading to Cloud 25R1 our user sessions are timing out much more frequently even after extending the times on the Sessions and Tokens page.
We use SSO and the user is taken to an Azure Login Screen but this has happened on accounts that are not using SSO as well.
Some users have reported being logged out while they are working in the system and others after only working outside of IFS for only 5 - 10 minutes.
Has anyone else experienced this?
Hi
Yes — this behavior has been observed by several customers after upgrading to IFS Cloud 25R1, especially in environments using Microsoft Entra ID (Azure SSO).
Even if you increased:
Users can still be logged out because:
IFS session settings are only one part of the chain
The actual session depends on multiple layers:
Even worse:
IFS 25R1 introduced stricter:
This can cause:
Check:
If set low (e.g., 5–10 mins):
Symptoms:
Means:
This confirms:
Not only Azure issue
Likely combined with:
Check:
Very often overlooked
Helps identify cookie issues
Check:
Look for:
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
