-
Notifications
You must be signed in to change notification settings - Fork 979
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
LDAP_DOMAIN and LDAP_BASE_DN discrepancy #172
Comments
Interesting, maybe related to #161 |
Yes, I forgot about this. Anyway, thanks for that image. It's this one who made me dive into LDAP as I'm trying to have 1 LDAP to kill them all (identification system). |
When environmentvariables have been set like this: LDAP_BASE_DN="o=some org,c=com" LDAP_DOMAIN="some-org.com" The base dn of the generated LDAP is dc=some-org,dc=com instead of o=some org,c=com This commit fixes that
Like said here, in order for If I use the following compose-file:
then I must write those 2 files into
|
Just to have all options in one place, I also commented on a similar issue where Basically, this line makes |
Hello,
Running containers from scratch with 2 settings would result in different results.
It seems if we set the LDAP_BASE_DN ourselves, it doesn't generate the LDAP base correctly.
I tried to investigate and the max I could see is that on that step in startup script the 02-security.ldif is well provisioned with the good LDAP_BASE_DN value. So I don't know what make the system create the default example.org admin account, but it must be around there…
The text was updated successfully, but these errors were encountered: