pgadmin-org / pgadmin-org/pgadmin4

Gravatar is based on username even if email is available

Open
#10,415 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
Python
Stars
3.8k
Forks
891
Avg merge
4d 7h
Merged PRs (30d)
8

Description

Please note that security bugs or issues should be reported to security@pgadmin.org.

Describe the bug

When a pgadmin user has an email address set (e.g. from an OAuth2 provider), the Gravatar shown in the user menu is still based on the local username, which may be different from the Gravatar username of the user (or worse, the local username matches a Gravatar username of a different person).

To Reproduce

Steps to reproduce the behavior:

  1. Ensure that SHOW_GRAVATAR_IMAGE = True
  2. Create a pgadmin user with a username for which no Gravatar profile exists, and a valid email address for which a Gravatar profile exists
  3. Log in as that user
  4. Observe a default Gravatar next to the user’s name

Expected behavior

When a user’s email address is known, it should be used as the Gravatar identifier.

Error message

Screenshots

Image

Desktop (please complete the following information):

  • OS: Alpine Linux v3.24, Linux-7.1.8-200.fc44.aarch64-aarch64-with-musl1
  • pgAdmin version: 9.17
  • Mode: Server
  • Browser (if running in server mode): Safari Version 26.6.2 (21624.5.1.11.3)
  • Package type: Container

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the user-menu Gravatar rendering and the SHOW_GRAVATAR_IMAGE setting, then identify where the Gravatar identifier is selected. Reproduce the issue with a user whose email has a Gravatar profile, and verify that the displayed image uses the known email rather than the local username.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.