[ZBX-21975] User auto logout is working incorrectly Created: 2022 Nov 24  Updated: 2025 May 20

Status: Fix for Manual Testing
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 6.0.11rc1, 6.2.5rc1, 6.4.0beta3
Fix Version/s: 6.0.41rc1, 7.0.14rc1, 7.2.8rc1, 7.4.0rc1 (master)

Type: Problem report Priority: Major
Reporter: Larisa Grigorjeva (Inactive) Assignee: Deniels Pankins
Resolution: Unresolved Votes: 7
Labels: SAML, authentication, login, logout, sessions, user
Remaining Estimate: Not Specified
Time Spent: 38.5h
Original Estimate: Not Specified

Attachments: PNG File Screenshot_15.png     PNG File Screenshot_16.png     PNG File Screenshot_17.png     PNG File Screenshot_18.png     PNG File Screenshot_19-1.png     PNG File Screenshot_19.png     PNG File Screenshot_20.png     PNG File image-2022-11-24-16-06-43-567.png     PNG File image-2025-04-23-18-26-53-061.png    
Issue Links:
Causes
caused by ZBXNEXT-5965 Zabbix UI and API must not keep any l... Closed
Duplicate
Related
Team: Team A
Sprint: S24-W38/39, S24-W46/47, S25-W2/3, S25-W4/5, S25-W6/7, S25-W14/15, S25-W16/17, S25-W18/19, S25-W20/21
Story Points: 1

 Description   

Session initialization error for SAML user after auto-logout.

  1. Login with SAML user. 
  2. Make the tab with this user logged in inactive (open another tab, or open another browser).
  3. In other browser login with Zabbix  admin user and change Auto-logout interval fot SAML user to 1m (just for not to wait 15minutes).
  4. Wait for more than 1 minute until SAML user gets auto-logged-out.
  5. Try to login SAML user once again and get error:
  6. Click Login again, get to login screen and try lo login with SAML again.
  7. Success login.

This is actual for both Okta and OneLogin.

 Comments   
Comment by Gregory Chalenko [ 2023 Jan 05 ]

Resolved in PR #4955.

Comment by Jānis Jansons [ 2023 Jul 24 ]

Any news on this? Still an issue in 6.4.4

Comment by Andrejs Verza [ 2023 Jul 24 ]

Hi, janhouse,

This issue shall be resolved prior to releasing 7.0.0.

Comment by Cloud Ops [ 2024 Feb 21 ]

We are still seeing this behavior in 6.4.12rc1.

Comment by Ilya S [ 2024 Apr 12 ]

6.4.13 - the problem is reproduced every time and not solved

Comment by Ali Berry [ 2024 May 16 ]

Problem still exists in 7.0.0rc1

Comment by Ali Berry [ 2024 Jul 08 ]

averza - any update on this? This is still present in the release version of 7.0.0.

Comment by Andrejs Verza [ 2024 Jul 11 ]

Hi, cloudops, elijahwood, aliberry!

I'm sorry we didn't resolve the issue before the release of 7.0. This task is once again in our priority list.

Comment by Ali Berry [ 2024 Sep 18 ]

Can this be marked this as unresolved until it actually is? I see that it's still not in the 7.0.4RC1 bug fixes and just keeps getting pushed out.

Comment by Ali Berry [ 2024 Nov 07 ]

averza - Any updates on this? Thanks!

Comment by Ali Berry [ 2025 Feb 12 ]

Hi there - are there any updates on this? This is still unresolved.

Generated at Thu May 22 08:11:48 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.