Hi Quanah, I am not sure how slapo-unique works. I am struggling with the syntax. How can I check current config concerning it?
Thanks and regards, Sandro -----Original Message----- From: Quanah Gibson-Mount <[email protected]> Sent: Wednesday, February 28, 2024 6:27 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 Wednesday, February 28, 2024 7:34 AM +0000 CALDEIRA JAVIEL Sandro <[email protected]> wrote: > Hi, > > I have a legacy ldap instance (openlda-2.4) which has in the same > redundant user info containing mail attribute among others (objectclass: > inetOrgPerson) in 2 different ous (objectclass: organizationalUnit). I > know it is a bad design for ldap users structure but I am not allowed > to change it in a short time. When I tried to migrate this ldap > database to openldap 2.6 I realize this is not possible anymore. I > identified it is just related to mail attribute because if I omit mail > attribute or use a different value for mail, then all data is imported properly. Do you use the slapo-unique overlay? The only uniqueness requirement on mail out of the box is that for any specific entry, the mail value must be unique. There is no requirement *across* subtrees that it be unique unless the configuration loads and uses slapo-unique to do this. If you have duplicate values for 'mail' within a given entry, then you need to fix that. --Quanah
smime.p7s
Description: S/MIME cryptographic signature
