Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-39854

Crowd user directory Trigger false Alarm: 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.

      First Symptom

      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.

      Steps to replicate

      1. Install Confluence 5.8.15
      2. Create a user directory with Crowd 2.8.2, Crowd internal Directory
      3. Preform a Test Remote Directory Connection

      Expected Behavior
      Test successful without any error/Warning

      Actual Behavior

      Crowd and Jira does not contain UUID for user, you can safely ignore this error message

            [CONFSERVER-39854] Crowd user directory Trigger false Alarm: 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.

            2022 year, anf bug still persist. 

            Сухоруков Александр added a comment - 2022 year, anf bug still persist. 

            I setup embedded crowd sync, this error did not apper.

            I also setup LDAP sync, with different group names, this error did not appear.

             

            Once I renamed the LDAP groups to match the name of the orginal groups (previously part of crowd-sync), then this error started appearing.

             

            Hope that helps.

            Simon Jackson added a comment - I setup embedded crowd sync, this error did not apper. I also setup LDAP sync, with different group names, this error did not appear.   Once I renamed the LDAP groups to match the name of the orginal groups (previously part of crowd-sync), then this error started appearing.   Hope that helps.

            Please fix this, showing the warning causes a lot of confusion.

            Axel Heider added a comment - Please fix this, showing the warning causes a lot of confusion.

            Atlassian dev team...I am a fellow developer and this should be a very easy fix in the back-end.  Let's get on the ball and FIX THIS please.  Having false negatives appears as if it is a configuration issue either caused by the end-user/administrator or faulty design of your system.  Either way, it should be fixed as the solution is quite evident as previously stated by an Atlassian team member.  I understand there are priorities and timelines, but bug fixes such as this one should be high on the priority list in my humble opinion.  Allowing it to linger for so long does not reflect well on your business.  Thank you.

            BetterPanel LLC added a comment - Atlassian dev team...I am a fellow developer and this should be a very easy fix in the back-end.  Let's get on the ball and FIX THIS please.  Having false negatives appears as if it is a configuration issue either caused by the end-user/administrator or faulty design of your system.  Either way, it should be fixed as the solution is quite evident as previously stated by an Atlassian team member.  I understand there are priorities and timelines, but bug fixes such as this one should be high on the priority list in my humble opinion.  Allowing it to linger for so long does not reflect well on your business.  Thank you.

            Hi!
            We have met with this issue.
            Where use case was connect Confluence 6.6.3 to Jira 7.8.0, as Jira external management.

            Any plans to see it?

            Thanks
            Gonchik Tsymzhitov

            Gonchik Tsymzhitov added a comment - Hi! We have met with this issue. Where use case was connect Confluence 6.6.3 to Jira 7.8.0, as Jira external management. Any plans to see it? Thanks Gonchik Tsymzhitov

            Ben Keene added a comment - - edited

            As of 10 July 2017 this is still an issue.  Please at least add text that this is a spurious warning when connecting to other Atlasssian software. (Seen connecting Bitbucket to Jira)

            Ben Keene added a comment - - edited As of 10 July 2017 this is still an issue.  Please at least add text that this is a spurious warning when connecting to other Atlasssian software. (Seen connecting Bitbucket to Jira)

              Unassigned Unassigned
              wwong Wayne Wong
              Affected customers:
              46 This affects my team
              Watchers:
              31 Start watching this issue

                Created:
                Updated: