You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating the container using e.g. --env LDAP_BASE_DN=o=inet --env LDAP_DOMAIN=inet the ldap server gets configured with olcSuffix: dc=inet and olcRootDN: cn=admin,dc=inet. This is a bug. Access rules are ok, e.g. olcAccess: {1}to * by self read by dn="cn=admin,o=inet" write by * none.
IMHO the LDAP_DOMAIN env should be dropped completely - the concept is simply wrong and buys nothing but confusion and bugs.
The text was updated successfully, but these errors were encountered:
@jelmd seem like you have hit one of the numerous issues linked to these variables. This is why I had created a discussion issue which sums up all these as well as some fix I made to do stronger checking on coherency between all these env variables values.
When creating the container using e.g.
--env LDAP_BASE_DN=o=inet --env LDAP_DOMAIN=inet
the ldap server gets configured witholcSuffix: dc=inet
andolcRootDN: cn=admin,dc=inet
. This is a bug. Access rules are ok, e.g.olcAccess: {1}to * by self read by dn="cn=admin,o=inet" write by * none
.IMHO the LDAP_DOMAIN env should be dropped completely - the concept is simply wrong and buys nothing but confusion and bugs.
The text was updated successfully, but these errors were encountered: