Skip to content
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

Readonly account doesn't work #64

Closed
kopax opened this issue Jun 29, 2016 · 2 comments
Closed

Readonly account doesn't work #64

kopax opened this issue Jun 29, 2016 · 2 comments

Comments

@kopax
Copy link

kopax commented Jun 29, 2016

With a fresh db install, I have the following :

openldap        | Add read only user...
openldap        | Processing file /container/service/slapd/assets/config/bootstrap/ldif/readonly-user/readonly-user.ldif
openldap        | adding new entry "cn=readonly,dc=domain,dc=com"
openldap        | Processing file /container/service/slapd/assets/config/bootstrap/ldif/readonly-user/readonly-user-acl.ldif
openldap        | ldap_modify: No such object (32)
openldap        | *** /container/run/startup/slapd failed with status 32
openldap        | 
openldap        | *** Killing all processes...

The creation fails with the files bootstrap/ldif/readonly-user/readonly-user-acl.ldif,

 dn: olcDatabase={1}{{ LDAP_BACKEND }},cn=config

With LDAP_BACKEND=hdb

But, the file 02-security.ldif which also has the same syntax work well.

I have tried to swap the content of files in every order, I wasn't able to make it work.

@kopax
Copy link
Author

kopax commented Jun 29, 2016

It appear that the problem comes from the fact that {{ LDAP_BASE_DN } is not available for create when the scripts try to execute it.

By moving it's content in a file bootstrap/ldif/99-perms.ldif, the user successfully create.
be careful to change the interpolated string as the startup script is hardcoded for using with old file

This could be fixed by being able to delay it's importation.

@osixia
Copy link
Collaborator

osixia commented Jun 30, 2016

Hello,
this will be fixed in the next release thanks to @danielpanteleit

see pull request #62

Thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant