Forwarded to devs Session Idle Time increase has no effect

[SKDamon]

TITLE:

Session Idle Time increase has no effect​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Plesk Onyx
Version 17.8.11 Update #15
Ubuntu 16.04 x86_64​

PROBLEM DESCRIPTION:

The configured session timeout value (Tools&Settings > Security > Session Idle Time) is not honored. When reloading or navigating on a page idle for >10min, I get logged out even though the Session Idle Time is set to 60 Minutes.​

STEPS TO REPRODUCE:

Follow the instructions to set Idle Time to 60 (minutes):
How to set session idle time in Plesk?

Leave any plesk page open for >10 Minutes

Navigate by clicking a link or refresh the page​

ACTUAL RESULT:

Login screen appears
(Redirect to the actual requested page after login fails in most cases, too)​

EXPECTED RESULT:

Requested page is loaded without authenticating again​

ANY ADDITIONAL INFORMATION:

I verified the value is set correctly in the database (How to set session idle time in Plesk?)

I'm using an admin account and checked "Allow IP address changes during a single session". I'm also using the Google Authenticator extension for 2FA login.​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

From developer:

Not reproduced. No any session idle time settings neither in extension code nor google account preferences.
It is may be Google Auth app issue or date&time settings misconfiguration on client machine.

 

[Jesse Messenger]

Can absolutely confirm this issue and it is a decent headache.


‪Ubuntu 16.04.5 LTS‬
Plesk Onyx
Version 17.8.11 Update #16

 

[trialotto]

Can absolutely confirm this issue and it is a decent headache.


‪Ubuntu 16.04.5 LTS‬
Plesk Onyx
Version 17.8.11 Update #16

@Jesse Messenger

Do you have the Google authentication extension installed? Might be some important piece of information for Plesk Team.

Regards.........

 

[SKDamon]

Hey,

That problem existed on my server back when I didn't have Google Auth installed.
Are there any logs or other info that would help confirm this as a bug?

Some time-related settings:

# ls /etc/timezone
4.0K -rw-r--r-- 1 root root 14 Nov 10  2017 /etc/timezone
# cat /etc/timezone
Europe/Berlin
# ls /etc/localtime
0 lrwxrwxrwx 1 root root 33 Nov 10  2017 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin
# date
Fri Aug 10 08:52:05 CEST 2018

The output of `date` yields my correct local time.
Panel.log doesn't show anything obviously related.

 

[trialotto]

@SKDamon (and @Jesse Messenger )

I have tested this on an Ubuntu machine....... and I cannot reproduce the behaviour reported by you........same result as @IgorG already told.

Kind regards........