pgadmin-org / pgadmin-org/pgadmin4
Using ldap without having an internal user and setting PGADMIN_DEFAULT_EMAIL and PGADMIN_DEFAULT_PASSWORD
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Why do I need to set PGADMIN_DEFAULT_EMAIL/PGADMIN_DEFAULT_PASSWORD for ldap?
It looks like type internal must always be part of the list and so the two mentioned parameters must be set to create an admin user. But why?
Is it not possible to just use ldap? And therefore a parameter like PGADMIN_DEFAULT_USERNAME could be set? Now if I'm right the value of PGADMIN_DEFAULT_EMAIL is used to set the username.
We would like to use pgAdmin without the possibility of creating internal users. Just LDAP-user.
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.
Research direction
Start by tracing how PGADMIN_DEFAULT_EMAIL and PGADMIN_DEFAULT_PASSWORD are processed alongside the internal and LDAP authentication types. Done means an installation can use LDAP without creating internal users or requiring those credentials, while providing an appropriate username setting if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100