The poster who gave you that advice is wrong. "replace" replaces the entire entry with what you've added. You want add: value, not replace: value, like you originally had.
Thanks Quanah for providing the correct answer. I could not find an example, and did not have a ldap server handy in order to test.
To replace the 12th index, you could do:
changetype: modify delete: olcAccess olcAccess: {11}
^ deletes the 12th index, since it is ZERO based. If you want the 13th index ({12}), adjust appropriately.
changetype: modify add: olcAccess olcAccess: {11} <new rule>
So in order to modify olcAccess: {11}, you first have to delete it and then re-add it? There is no way to modify it in place and change its contents?
Thanks /Cole
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc.
Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
--On Tuesday, March 15, 2016 1:58 PM +0200 Cole cole@opteqint.net wrote:
To replace the 12th index, you could do:
changetype: modify delete: olcAccess olcAccess: {11}
^ deletes the 12th index, since it is ZERO based. If you want the 13th index ({12}), adjust appropriately.
changetype: modify add: olcAccess olcAccess: {11} <new rule>
So in order to modify olcAccess: {11}, you first have to delete it and then re-add it? There is no way to modify it in place and change its contents?
No. What I generally do is read the value, store that, tweak it how I want, and then write it back (delete, add modified value). What's handed with the way things are ordered in cn=config is that you don't have to run the delete command against the full exact value, but only the index.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
openldap-technical@openldap.org
-
Cole -
Quanah Gibson-Mount