Setting username via OAuth on shared servers
Maintainers usually reply within 2 days
@excalq is already working on this.
Since Jan 16, 2026.
Assessment
This issue has not been assessed yet.
Description
We have a use case of providing users with pre-configured database connections, which shared servers works well for. However, each user has a separate account in these databases, matching the email in their OAuth authentication flow (via Auth0). Their passwords are sourced externally (aws rds generate-db-auth-token) and short-lived, so we only need to set usernames, not passwords.
I was attempting to set a configuration to achieve this using servers.json, but it does not appear possible, looking at the codebase. We don't want a shared username, nor does Username: null cause the email/oauth-username-claim to be used, instead username is missing, and 'must be specified'.
The goal: Use the value of OAUTH2_USERNAME_CLAIM for Shared Servers instead of SharedUsername.
Related Issue: Shared Usernames: #6229
Describe alternatives you've considered
- Provisioning non-shared databases, per user: The servers.json is loaded into the SQLite DB once, as I understand, and removing it has undesired consequences, so this would be burdensome when adding new users.
Additional context
I am willing to contribute a PR with some changes in ServerModule.create_shared_server, but would like to open this discussion first.
- Dominant language
- Python
- Stars
- 3.9k
- Forks
- 922
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 33
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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
-
Invalid syntax in sshtunnelPossibly taken A pull request linked to this issue is open or already merged. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pgadmin-org/pgadmin4#10797 ·
Maintainers usually reply within 2 days
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgadmin-org/pgadmin4#10426 · 3 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
pgadmin-org/pgadmin4#10796 · 1 comment ·
Maintainers usually reply within 2 days
-
Schema Diff does not detect foreign keys that reference a different schemaPossibly taken @dpage claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 57/100
pgadmin-org/pgadmin4#10786 · 1 assignee ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
pgadmin-org/pgadmin4#10783 ·
Maintainers usually reply within 2 days
All issues in pgadmin-org/pgadmin4
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openedx/xblock-lti-consumer#765 ·
Maintainers usually reply within 1 day