Can we adjust the session expiration interval in IFS Cloud?

Hi @Buddhika Kurera 

Thanks for your quick reply.

However, when we select this row, there is no "Modify" button available for updating.

Best regards,

Feng

Can someone confirm whether or not we can modfiy the timeout value? 

Hi @Alex Ivkovic 
 

Thank you for following up.

Best regards,

Feng

Hi all,

Could you give me an update? Thanks!

I cannot modify timeout value.

Best regards,

Feng 

Hi all,

Is there a update on this topic? The modify button is not available (24R1)

Hello ​@Buddhika Kurera

Is there a update on this topic? Our IFS environment is on 24R2  and  the option to modify is disable.

Regards

​@Buddhika Kurera 

This should not be marked as ‘Solved’ since the issue is not solved.

The two system parameters introduced in 23R2 in the category ‘Security’ are still not editable even in version 25R1. 

How can we edit these parameters:

‘Time a session is allowed to be idle before it expires’

and 
‘Max time before a session is expired. Default value is 36000’

or how can we adjust the expire-times of sessions?



 

Reason it can’t be modified is because this parameter is set as a client read only field (i.e. not allowing people to modify it from the client)

So, yeah, the fact you can’t modify it is inteded as far as IFS is concerned unless R&D changes their mind and sets that value to FALSE in the database to allow users to modify them.

I mean obviously you could customize this with a simple database script to change the client_read_only column to FALSE, which would then allow you to edit it in the client, but I make no promises as to whether this will have any impact at all, either positive or negative.

I found out that the parameters were introduced in 23R1 but the ability to change the values was introduced later (24R2?).

Changing time-out values is done in ‘IAM Sessions and Tokens Configuration’.

Explained in more detail here:
https://docs.ifs.com/techdocs/25r1/030_administration/010_security/040_iam_settings/085_iam_configuration/040_sessions_and_tokens/

This is the information I was hoping to get through this community post.

Thank you for this.

Can you confirm that this also applies to sessions that are connected through SSO rather than direct IFS IDP?