Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

The Unique ID Attribute has been left blank

I'm trying Confluence.

in "Test Remote Directory Connection"

If I test the connection I see these results:


Test basic connection : Succeeded


  Test retrieve user : Succeeded


 Test user rename is configured and tracked : The Unique ID Attribute has been left blank. We recommend you set this to the attribute for the UUID of the user.


  Test get user's memberships : Succeeded, 1 groups retrieved


  Test retrieve group : Succeeded


  Test get group members : Succeeded, 2 users retrieved


  Test user can authenticate : Succeeded

I'm not sure what to do.


1 answer

0 votes
Mallmann Atlassian Team Mar 04, 2015

Hello Jialu,

Can you let us know which LDAP directory you are using on your Confluence?

The User Unique ID Attribute field is the attribute objectGUID on Active Directory and is located under the User Schema Settings of your LDAP configuration on Confluence.

However, it depends on your LDAP to exist and it also might be a different attribute.


I hope it helps. smile


what if we are not connected to LDAP? Using Atlassian Crowd internal directory.

Not connected to LDAP.  Using Atlassian Crowd and getting this error.  So, why isn't crowd configured properly?

Doesn't work with JIRA either. You would think that Atlassian could make their own products mutually compatible.

Mallmann Atlassian Team Apr 21, 2015

Hey guys, JIRA and Crowd do not use this field to rename users, thus you guys are seeing this message. So, there's no need to worry about this warning. :) The warning appears because the tests are the same ones run against the LDAP or any other directory type. I hope it clarifies. Eduardo

Why can't Atlassain care about such things and not bother user with false warnings? As mentioned above "why can't you get work your own products products together?".

I agree. Can we please get a fix if using Jira or Crowd directories to authenticate? Having a false positive has obviously wasted a lot of administrators time already

False positive warnings that are irrelevant are an unnecessary distraction and will cause more harm than good. If a directory doesn't provide a particular field, don't test for it.

It shouldn't be a problem to add a pre-stage to the test, checking the type of directory, then test for the uid field only if relevant.

An even easier solution and still acceptable in my opinion would be to simply add to the error message a short line: "if not using LDAP disregard this message" or something like that.

Also comes up if you mount the directory read only; assuming the settings were preserved it's not a huge deal, but it's definitely off-putting. 

This problem now seems to block the Crowd sync between crucible, confluence, Bitbucket and Jira, where JIRA is the Crowd server.

This error appears in the error log:

Multiple entries with same key:

It is actually the same user, created date is the same, however the loginname changed (for as far as i can see). In JIRA the issue not there, the user is only visible once, but in crusible 2 seem to exist. Please help because the problem is blocking!

This error has also caused me grief and looks bad on the company in my opinion, almost as bad as this thread. Starting to remind me of a Google or Microsoft forum, where nobody responds. How about, "we understand your input and are looking to resolve this in a future release"? Make a JIRA ticket and get er done!

Mallmann Atlassian Team Nov 28, 2016

We already have a ticket open to report and track this behaviour right here:

Feel free to comment on that ticket.



just stepped over this funny task here as this message is still wasting administrators time. 2 years after opening a ticket on it....

Like Carl_St-Laurent likes this

still the same 4 years later

Like Nikusha Melikidze likes this

And in 2021, we're still gonna be...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

🥓🙅🏻‍♀️ Meet-less May Badge!

Hello Confluence Community!  What if i told you that you could have a healthier life and be 100% meet-less? This month, we're promoting a healthy, balanced work diet with Confluence. (Read m...

447 views 3 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you