-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/postgresql] Postgres LDAP does not create role by it's own #72707
Comments
Hi, Could you provide us with a docker-compose that clearly reproduces the issue? We need to understand whether it is an issue in the Bitnami packaging of PostgreSQL or in PostgreSQL itself. |
Hi, the origin of this issue comes form using helm chart, but I was able to reproduce it with very basic container configuration. Here's my podman run command I'm sure LDAP works as expected
|
Hi @Diegunio, As far as I know, the LDAP settings do not create roles and databases for the users in your LDAP server. I used this sample scenario: services:
ldap-server:
image: ghcr.io/rroemhild/docker-test-openldap:master
postgresql:
image: docker.io/bitnami/postgresql:17
environment:
- POSTGRESQL_PASSWORD=postgres
- POSTGRESQL_ENABLE_LDAP=yes
- POSTGRESQL_LDAP_SERVER=ldap-server
- POSTGRESQL_LDAP_PORT=10389
- POSTGRESQL_LDAP_BASE_DN=ou=people,dc=planetexpress,dc=com
- POSTGRESQL_LDAP_BIND_DN=cn=admin,dc=planetexpress,dc=com
- POSTGRESQL_LDAP_BIND_PASSWORD=GoodNewsEveryone
- POSTGRESQL_LDAP_SEARCH_ATTR=uid
client:
image: docker.io/bitnami/postgresql:17
command:
- 'tail'
- '-f'
- '/dev/null' Until I got the same error:
The error was fixed after I logged in as
After that, login succeeds using LDAP user password:
Maybe what your use case requires some additional scripting or external tools such as pg-ldap-sync |
Name and Version
bitnami/postgresql:16.4.0
What architecture are you using?
amd64
What steps will reproduce the bug?
What is the expected behavior?
LDAP user's role is created by it's own
What do you see instead?
connection failed: connection to server at "192.168.215.1", port 5432 failed: FATAL: role "name.lastname" does not exist
Additional information
No response
The text was updated successfully, but these errors were encountered: