Repository navigation
Issue with sessions in pgAdmin4 #6090
Description
Please note that security bugs or issues should be reported to [email protected].
Describe the bug
An issue with pgAdmin4 sessions
To Reproduce
Steps to reproduce the behavior:
- Install pgAdmin 4 (v6.21) using wheel package (considering all fresh pgAdmin setup)
- Create a user ([email protected]) and login
- Add new Servers (using import/export servers) and connect with the server
- Keep open the browser windows with the [email protected] user logged in
- Now uninstall pgAdmin and remove the DB file as well
- Now Install pgAdmin 4 v7.0
- Create a user ([email protected]) and log in
- Add new Servers (using import/export servers)
- check the server which was connected with V6.21 is showing as connected even though we have not connected it with the latest installation.
Expected behavior
It should not use the older session with the new login
(Note: use fs_uniquifier from the User model to create a new session)
Desktop (please complete the following information):
- OS: OSX Ventura
- Version: Candidate build V7.0
- Mode: Server
- Browser (if running in server mode): chrome
- Package type: Python
Activity
1 remaining item
dpage commentedon Aug 19, 2026
Root cause traced and PR up: #10312. The cached
ServerManagerfor a session is looked up by session id + numeric server id only, so if the configuration database is reset/restored without restarting pgAdmin, a newly created server can inherit a deleted one's id and get served its stale, still-cached connection manager. The fix compares the manager against the current server row's identifying fields before reusing it.fix: bind cached server managers to the pgAdmin user
fix: bind cached server managers to the pgAdmin user
fix: bind cached server managers to the pgAdmin user
Refresh a stale ServerManager when a server id is reused. pgadmin-org…
Refresh a stale ServerManager when a server id is reused. #6090 (#10312)
dpage commentedon Oct 13, 2026
Fixed by #10312 (3d5661e).