I have an issue with Mobile Access Configuration, What ever I change the session expiration to it always stays at the default time of 5 minutes

I just tried running Aveva Edge 2020R2 SP2 P01 on a different machine, and the result is the same.  No matter what value the "Session Expiration" is set to, the time out happens after 300 seconds (5 minutes).

Shawn, Thanks for the follow up. If this is an urgent issue I would suggest you contact our (AVEVA) customer support.

I worked with a couple of our R&D team members and we tried both AVEVA Edge 2020 R2 SP2 P01, and 2023 R2 (beta). I just realized as I am typing that you mentioned 2020 R2 P01 (without the Service Pack). I am checking if they can try it with 2020 R2 P01.

In both versions we tried, it worked as expected. Under and over 300 seconds worked. For example, I have this test set to 3600 and it has been running for 45 minutes:

I am curious, how are you checking if the session has timed out? and under what conditions? What do you see that lets you know the session is expired?

Scott

Hi Scott Kortier , what the function or program are you using to see the sessions ?

In the system tray there is an icon for "Mobile Access Task": 

Scott

When the logon dialog appears in the browser, prompting the username and password to be entered again.

Below is what happens between 5 and 6 minutes after I login:

.

As for the version, it says Service Pack 3 in the about:

It looks like I found the solution in the Security System Configuration:

Even though I have the Log On after set to 0 minutes, the runtime still seems to pay attention to the "Disconnect web thin client on auto log off" check box and enforces the default 5 minute Session Timeout in Mobile Access.

However.... I just noticed the user changed from Admin to Guest after 6-7 minutes:

Perhaps the work around is if I set both the Log off after time and Session Timeout time both to 3600 and see the result.

It looks like I found the solution in the Security System Configuration:

Even though I have the Log On after set to 0 minutes, the runtime still seems to pay attention to the "Disconnect web thin client on auto log off" check box and enforces the default 5 minute Session Timeout in Mobile Access.

However.... I just noticed the user changed from Admin to Guest after 6-7 minutes:

Perhaps the work around is if I set both the Log off after time and Session Timeout time both to 3600 and see the result.

I just saw my mistake!  The Admin group has a auto log out time of 5 minutes.

That's better!

Shawn,

Thanks for following up, and posting how you solved it!

And, for using Heroes HQ!

Scott