Nevermind think I figured it out and added the acl on the openldap side. From: Wu, Andy via Lam-public <lam-public@lists.sourceforge.net> Date: Monday, April 21, 2025 at 2:57 PM To: Lam-public@lists.sourceforge.net <lam-public@lists.sourceforge.net> Subject: [EXTERNAL] [Lam-public] Cannot make changes to ldap So I have a group of users that cannot make changes to openldap with insufficient access. There are 2 set of server profiles and each profile is exactly same with two different group of users. One group of users can write another group of users ZjQcmQRYFpfptBannerStart Warning! This email comes from outside the company. This message came from outside of Itron, if you suspect it to be spam, please delete it or if you suspect a phishing attempt, please report it using the Phish Alert Report button. Be careful and think before you click.
ZjQcmQRYFpfptBannerEnd So I have a group of users that cannot make changes to openldap with insufficient access. There are 2 set of server profiles and each profile is exactly same with two different group of users. One group of users can write another group of users cannot. Both profile is using the same bind user and password. IS there something I’m doing wrong or do I need to add the acl of the group directly to the openldap acl ?
_______________________________________________ Lam-public mailing list Lam-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lam-public
