• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Forwarded to devs Session Idle Time increase has no effect

SKDamon

Basic Pleskian
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
 
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.
 
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:
Code:
# 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.
 
Back
Top