-
Notifications
You must be signed in to change notification settings - Fork 121
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
Add memberOf using customSchemaFiles: ->ldap_modify: No such object (32) #134
Comments
I'm facing the same issue. |
Trying to do the same thing, been deep diving on it. Still not working. From the base image side at least it should be doable. bitnami/containers#982 |
I figured it out finally, this is how you do it
|
Only adding the custom schema files does not appear to do anything for me. Could you show the rest of your configuration? |
Hi @seang96
Run: You should get :
Let me know if this is working for you, i'll update the advanced configuration and I'll plan to add an enabler in the values to ease the configuration |
Looks like it did not work for me. I started namespace / helm install from scratch with no PVC. LDAP response:
Helm install info:
Initial startup logs: (It fails to import everything, database is not a shadow)
values.yaml:
|
I see that replicaCount is 1 , did you disable the replication ? |
Yes for quicker testing since you have to wipe the PVC |
Ok can you post your full values file ? |
That was my values.yaml file for testing. As for my real one I am also intending to load in rfc2307bis using ldif file from https://github.com/osixia/docker-openldap in my production config. I am currently using that docker image for my setup that is not HA. |
Alright, in that case can you add the following in your values to disable the replication :
|
Running with replication false I still get an error Logs on initial pod creation
LDAP response
|
I have the exact the same issue, and the workaround provided by @jp-gouin does not work neither. It looks like syncprov module is configured after import of custom schemas, thus overwriting the cn=module{0},cn=config attributes. |
Based on your test @jp-gouin , I retried. I'm also failing. For troubleshooting purposes I ran it with this command: cat <<EOF > /tmp/schema.ldif
dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: memberof
EOF
ldapmodify -Y EXTERNAL -H ldapi:/// -f /tmp/schema.ldif and got:
Currently I run bitnami/openldap 2.6.3, as non-root - what magic did you do that it works on your machine ? And after Updating to 2.6.6, still as non-root - i get this using the snipped above:
and see this in my log on K8S:
|
Based on the quoted comment below of @GabeChurch , I could overcome problems adding the customSchemaFiles. But I had to do a tweak!
The next two ldifs for:
But this is only an intermediate step. A proof that it really works is waiting for time. I need to know two ldifs that create a user and a group and a way to assess if memberof works. If somebody reads this and can append such a test, that would help certainly :-)
|
Hi, I've compiled the following guide to use Examples of MemberOf configurationEnable MemberOf using replicationUse the following values to enable
Connect to your openldap instance and execute:
You should get the following result:
Enable MemberOf without replicationWhen the replication is disabled, the
Use the following values to enable
Connect to your openldap instance and execute:
You should get the following result:
|
Using the exact config for replica from your comment I get an error that causes the pods to crash on first initialization. memberof doesn't work afterwards either.
|
Hi , Please take a look at memberOf documentation |
Using version 4.1.2, my bitnami container bitnami/openldap 2.6.3 is unwilling to apply the provided schema.
The goal is to add "memberOf" to the LDAP by adding this to the values.yaml.
Than, when I apply it, the pod logs the following error and restarts the ldap server. However, the server after the crash doesn't know about its misery and starts in a incomplete configuration.
I'm unsure whether this is a chart problem but I can imagine that other might also like to see the solution when using this chart. I already googled and found input on the bitnami/openldap container project but i can't apply it with this chart.
Do you have any idea what's wrong with the ldif? (or with the chart). Thanks for help!
The text was updated successfully, but these errors were encountered: