[LOG_AUTHENTICATED_USER] missing name when logout
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- authentication, backend
Research direction
Start with the /logout and /oauth2/logout entry points and trace how LOG_AUTHENTICATED_USER adds usernames to request logs. Reproduce both logout flows with the setting enabled, then add or update coverage for the expected access-log username. Done means both logout requests log the authenticated username before the session ends.
Written by the indexing model from the issue text.
Description
Please note that security bugs or issues should be reported to security@pgadmin.org.
Describe the bug
Hello,
sine the new feature to log authenticated user has been done here, it seems that when you logout, username is not displayed in log.
Here an example with logout from oauth2:
1.2.3.4 - - [11/Sep/2026:06:37:07 +0000] "GET /oauth2/logout?next=/browser/ HTTP/1.1" 302 6269 "https://pgadmin4.youpi.fr/browser/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
Here an example with "classical" logout:
1.2.3.4 - - [11/Sep/2026:06:34:21 +0000] "GET /logout?next=/browser/ HTTP/1.1" 302 205 "https://pgadmin4.youpi.fr/browser/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
To Reproduce
Deploy pgadmin4 and enable LOG_AUTHENTICATED_USER, click on Logout button.
Expected behavior
Add missing username in log:
1.2.3.4 - me@youpi.fr [11/Sep/2026:06:34:21 +0000] "GET /logout?next=/browser/ HTTP/1.1" 302 205 "https://pgadmin4.youpi.fr/browser/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
Desktop (please complete the following information):
- OS: Kubernetes 1.34.8
- pgAdmin version: 9.17
- Mode: Server
- Browser (if running in server mode): Chrome/152.0.0.0
- Package type: Container
Thanks a lot
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pgadmin-org/pgadmin4
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgadmin-org/pgadmin4#10426 · 1 comment ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
pgadmin-org/pgadmin4#10424 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pgadmin-org/pgadmin4#10418 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
pgadmin-org/pgadmin4#10408 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pgadmin-org/pgadmin4#10401 ·
All issues in pgadmin-org/pgadmin4
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100