Hi Geert, You are right. phpldapadmin was blocking this import. I ran manually ldapadd and it worked.
Thanks a lot @Geert Hendrickx and @Quanah Gibson-Mount for your tips and analysis. KR Sandro -----Original Message----- From: Geert Hendrickx <[email protected]> Sent: Friday, March 1, 2024 9:28 AM To: Quanah Gibson-Mount <[email protected]> Cc: 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 Thu, Feb 29, 2024 at 14:55:57 -0800, Quanah Gibson-Mount wrote: > 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: Could that error just be a client-side check performed by phpldapadmin? The wording "value would not be unique" is not an OpenLDAP server error. On Wed, Feb 28, 2024 at 07:34:59 +0000, CALDEIRA JAVIEL Sandro wrote: > Error from phpldapadmin: > > Attribute value would not be unique > This update has been or will be cancelled, it would result in an > attribute value not being unique. You might like to search the LDAP > server for the offending entry. (Search) warn LDIF text import Could > not add object cn=*****,ou=Users,ou=TRG01,dc=***,dc=*****,dc=** > LDAP said: Success > Error number: 0x00 (LDAP_SUCCESS) > Description: The operation completed successfully. Geert
smime.p7s
Description: S/MIME cryptographic signature
