How to change Max Idle time in IFS Cloud

Hi @HoiIndikW,

There is no way of doing this in IFS Cloud 21R2. At least not yet. The default values are set as below,

Session Idle is 2 hours, SSO Session Max is 10 hours and Access token time span is 1 hour.

Hi @HoiIndikW ,

As noted above by @Himasha Abeywickrama , the the default timeout values have been defined in the 

default identity provider. As the access token life span is set to 1 hour, the user will be prompted to login again to the application if the client is left idle for more than 1 hour.  These values in identity provider have not been exposed in the application and hence not configurable at the moment. 

Hope this helps!

Thanks,

Kasun

Hi @Himasha Abeywickrama and @Kasun Balasooriya,

Thank you for your answers.

Best regards,

Indika 

@Himasha Abeywickrama Has this changed for 23R2?

@MELuther A system parameter has been added in 23R2 to control the timeout value.

@Roel van Zwieten FndSettings is fully granted to the permission set I have. I can see the system parameter, but it is not editable. Other parameters are editable.

Which parameter are we talking about? Both of these cannot be edited.
 

BTW, if the first parameter parameter on this list is linked to Oracle max_idle_time, has the second one had its counterpart somewhere?

So did we get an adjustable idle time in 23R2 or not?

Does anyone know who to edit those values in the system parameter?
 

This still doesn’t seem to be possible, even in 24R1 (just checked).
No way to edit the values.

But as there is a parameter and that is the actual value that's used it should be possible to change it from SOMEWHERE.

In on-prem, could it be changed from the database?

Would managed cloud change it if requested with a ticket?

Or where are the defaults defined? Do you need to do a delivery in order to get it changed?

Hi @SamiL 

we have the same problem. Have you any news about this problem?

Thanks,

Petr

No news. Just checked a 24R2 demo env and it doesn’t seem to be changeable at least in the current version. It now displays a default value of 1800 (seconds, ie. 30min) .

You could get an official answer from R&D by requesting this information, or instructions to change the idle value, with a support ticket.
Please post the CS-ticket number here in case you do.

There is now an Academy training in https://ifs.sabacloud.com/Saba/Web_spf/EU2PRD0185/app/content-player?contextid=ctctx000000002513199&subscriptionid=ctnsr000000000067108&assignmentid=cninv000000000031141&launchpoint=LEARNER&regid=regdw000000001231377&signOff=false&spfurl=false&backurl=me%2Flearningeventdetail%2Fcours000000000019695%3FregId%3Dregdw000000001231377%26learnerId%3Demplo000000000090421%26context%3Duser

promoting a IAM Sessions and Tokens Configuration -feature in 24R2.

Max session time can be extended to up to 24h, although 10h is recommended.

Docs (public) in https://docs.ifs.com/techdocs/24r2/030_administration/010_security/040_iam_settings/085_iam_configuration/040_sessions_and_tokens/#general_session_and_token_timeouts .

IAM Sessions and Tokens Configuration are good for service users while used for integrations. No way to change the session time for a real body hand-on in Aurena.