Description:
While conducting an LDAP integration test, There is the following issue: the test for "User Account Information Retrieval" fails with the message "Failed." The logs indicate a warning:
Caesium-1-4 WARN ServiceRunner [c.a.t.healthcheck.concurrent.SupportHealthCheckProcess] Health check 'Duplicate User Account' failed with severity 'warning': 'One or more duplicate user accounts found in the connected user directory.'
However, upon checking for duplicate accounts, I find no duplicates present. Despite the test failure, the actual synchronization works correctly.
Steps Taken:
Question: Has anyone else experienced this issue? What could be causing the warning about duplicate accounts despite successful synchronization? Any insights or suggestions would be greatly appreciated!
While conducting an LDAP integration test, I encountered an issue where the test for "User Account Information Retrieval" fails with the message "Failed." The logs show a warning:
Hi @yj_seong ,
First of all, synchronization can be successful since the log indicates that is a "warning", even if it is a severe one.
What is your identifier (User Unique ID Attribute) in your Jira configuration for these LDAP users? Maybe the identifier is let's say sAMAccountName while you are looking for duplicate CNs in LDAP. You can check the LDAP accounts by that attribute.
However, there is a great stuff in Jira Rest API for this issue. You can check duplicated users through "/rest/api/2/user/duplicated" endpoint:
curl -X GET "<BASE_URL>/rest/api/2/user/duplicated/list" \
-u "<USERNAME>:<PASSWORD>"
This will give you the list of duplicated users.
Also, you can go to the request from your browser. After logging in to Jira, just copy the link (after changing <BASE_URL>) to your browser and it will give the list.
For more details, you can refer to this knowledge base document.
Hi, @Salih Tuç
Thank you for your feedback. I’ve already checked for duplicate users using the REST API, and there are no duplicates.
I also forgot to mention that we already had LDAP set up, and after adding OpenLDAP, this is what happened when we performed the connection test on the new LDAP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.