Hi Quanah, Since it has side effects in customer side is there any workaround I could add to ignore this validation?
KR Sandro -----Original Message----- From: Quanah Gibson-Mount <[email protected]> Sent: Thursday, February 29, 2024 11:56 PM To: CALDEIRA JAVIEL Sandro <[email protected]>; [email protected] Subject: RE: Disable uniqueness for mail Attribute [You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] --On Thursday, February 29, 2024 8:11 PM +0000 CALDEIRA JAVIEL Sandro <[email protected]> wrote: > Hi Quanah, > > I am running openldap from bitnami docker - > https://github.com/bitnami/containers/tree/main/bitnami/openldap/2.6/d > ebi > an- 12 > > So there is not slapd.conf: > $ slapcat -n 0 > could not stat config file > "/opt/bitnami/openldap/etc/openldap/slapd.conf": No such file or > directory (2) > slapcat: bad configuration file! So clearly not using slapd.conf. I realize you do have to specify -F /path/to/slapd/config for the slapcat to work. But since you searched the config and there's no slapo-unique loaded, you're not using it. This would imply that your database has bad data in it, where there are duplicate values for the "mail" attribute IN a single entry like: uid=joe,ou=whatever,dc=example,dc=org ... mail: [email protected] mail: [email protected] Would count as duplicates, for example. Most likely validation checks during slapadd were improved between 2.4 and 2.6, so those errors are now being caught. You'll need to clean your database to be correct. --Quanah
smime.p7s
Description: S/MIME cryptographic signature
