By: Aleksandar Petkovski user 17 Dec 2018 at 7:24 a.m. CST

4 Responses
Aleksandar Petkovski gravatar
Hello, We have two different OpenLDAP servers and and a cache refresh process in order to authenticate to these two servers. Gluu is configured with openDJ and has a defined unique identification parameter in uid. So, it should be possible to for example configure 100 users in each of the backend servers, with each of the users having a different uid. As we do it, cache refresh still doesn't work, with a message: ``` Caused by: com.unboundid.ldap.sdk.LDAPException: A unique attribute conflict was detected for attribute mail: value bot000003@xyz.com already exists in entry inum=@!6F0C.513B.10DB.DE85!0001!0C7C.41B2!0000!7DC0.5335,ou=people,o=@!6F0C.513B.10DB.DE85!0001!0C7C.41B2,o=gluu ``` When I define a unique mail for each of the user, CR works and there are 100+100=200 users registered on gluu. Our wish is to be possible to use same email on two different LDAP servers, and use just the uid as a unique parameter. Is the mail attribute hard-coded in gluu to have a unique value or can this option (uniqueness) be changed (configurable)?

By Mohib Zico staff 19 Dec 2018 at 7:16 a.m. CST

Mohib Zico gravatar
I think there is some switches there to allow this multiple attribute... I'll try to find that out.

By Aleksandar Petkovski user 21 Dec 2018 at 4:27 a.m. CST

Aleksandar Petkovski gravatar
Hi, Mohib. Any news on this?

By Mohib Zico staff 21 Dec 2018 at 4:41 a.m. CST

Mohib Zico gravatar
It's in my ToDo list, will try to share info as soon as I can manage some time for community support.

By Aleksandar Petkovski user 14 Jan 2019 at 6:42 a.m. CST

Aleksandar Petkovski gravatar
Hi, Mohib. Just to add to this ticket, I found that it is not possible to log a user if it doesn't have configured a mail attribute, even though it should be possible to do this only with uid configured. I did not found anywhere in the documentation that a mail attribute is a necessary attribute for user identification. Please inform me also about this workaround.