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

After change an username in Active Directory and resynchronize, there are two accounts showing in Confluence (the old and the new username).

      Problem

      Steps to reproduce:

      1. At AD, rename a user.
      2. Try to re-sync the directory, note that both usernames (the old and the new username) are showed at Manage Users link.
      3. The new username didn't inherit the groups membership, the old username kept the group membership, but none of them can log in Confluence.

      Note: Even trying to resynchronize the directory many times and flush cache statistics (Confluence Admin > Cache Statistics > Flush All), don't seems to solve the problem.

      Fix

      There is none yet.

      Workaround

      1. At User Directories link, disable the directory, enable it again, and re-sync.
      2. Check the users at Manage Users link, it should now show only the right username, with the right group membership.

      Note there are cases where just disabling, enabling and syncing again does not resolve the issue. In those cases:

      • Database table may show 2 different users (due to rename) with the same external_id:
        SELECT * FROM cwd_user WHERE external_id in  (SELECT external_id FROM cwd_user GROUP BY external_id HAVING COUNT(*) > 1);
        

      Wokraround:

      1. Disable the current user directory
      2. Create a new user directory with the exact same configuration as it was in the old directory
      3. Sync the new directory and the users should be able to login and have the correct information.

            [CONFSERVER-22515] After change an username in Active Directory and resynchronize, there are two accounts showing in Confluence (the old and the new username).

            Dylan Evans added a comment - - edited

            This still problem exists in Confluence (v6.0.5) when JIRA's user directory is linked to AD and Confluence's User is linked to JIRA (v7.1.6). 

            I guess I'll need to create a new ticket but it's shocking that this problem still exists 2 years on from the last entry.

            Dylan Evans added a comment - - edited This still problem exists in Confluence (v6.0.5) when JIRA's user directory is linked to AD and Confluence's User is linked to JIRA (v7.1.6).  I guess I'll need to create a new ticket but it's shocking that this problem still exists 2 years on from the last entry.

            Thanks everyone for your feedback. This bug report relates to Confluence pre-5.3, when user rename was implemented. User rename is now working successfully when Active Directory is linked directly to Confluence. There is one ongoing issue with Active Directory creating a new user instead of renaming, but it only occurs when AD is linked to Crowd, and then to Confluence. It is being tracked in CONF-33455.
            As this bug report is now obsolete, we are going to close it to avoid confusion between the two tickets. If you are affected by the AD > Crowd > Confluence issue, please vote and add yourself as a watcher to CONF-33455. The ticket contains a workaround, and any further progress on the issue will be tracked in there.
            Thanks again for your input and patience.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - Thanks everyone for your feedback. This bug report relates to Confluence pre-5.3, when user rename was implemented. User rename is now working successfully when Active Directory is linked directly to Confluence. There is one ongoing issue with Active Directory creating a new user instead of renaming, but it only occurs when AD is linked to Crowd, and then to Confluence. It is being tracked in CONF-33455 . As this bug report is now obsolete, we are going to close it to avoid confusion between the two tickets. If you are affected by the AD > Crowd > Confluence issue, please vote and add yourself as a watcher to CONF-33455 . The ticket contains a workaround, and any further progress on the issue will be tracked in there. Thanks again for your input and patience.

            The workaround can cause issues with group memberships if using JIRA as a secondary user directory.

            Alan Whited added a comment - The workaround can cause issues with group memberships if using JIRA as a secondary user directory.

            still the same issue on 5.7.4

            Salmat Digital Systems Administrator added a comment - still the same issue on 5.7.4

            I wondering how it comes that a bug like this is still in the Open state, not even marked as Verified.

            Sorin Sbarnea (Citrix) added a comment - I wondering how it comes that a bug like this is still in the Open state, not even marked as Verified.

            intersol_old added a comment -

            Still refusing to fix the bug after more than 3 years? Here is another P1 support ticket that was partially caused this this CWDSUP-10063

            intersol_old added a comment - Still refusing to fix the bug after more than 3 years? Here is another P1 support ticket that was partially caused this this CWDSUP-10063

            ssearcy, david.sorenson, thanks for the additional information. My main concern was ensuring you weren't encountering a bug we had already fixed in a later version of the software. It sounds like this isn't the case.

            The problems you are having certainly sound like a bug but not one we seem able to easily replicate. The next steps would seem to be to gather more specific information about your particular configurations, which was why I suggested a Support interaction.

            There are probably a good number of configuration files, LDAP schema, DB configuration and other such details we will need to gather from you to try and get into a position where we can observe this same problem which it is generally better to do on a specific Support ticket rather than this publicly accessible bug report.

            Paul Curren added a comment - ssearcy , david.sorenson , thanks for the additional information. My main concern was ensuring you weren't encountering a bug we had already fixed in a later version of the software. It sounds like this isn't the case. The problems you are having certainly sound like a bug but not one we seem able to easily replicate. The next steps would seem to be to gather more specific information about your particular configurations, which was why I suggested a Support interaction. There are probably a good number of configuration files, LDAP schema, DB configuration and other such details we will need to gather from you to try and get into a position where we can observe this same problem which it is generally better to do on a specific Support ticket rather than this publicly accessible bug report.

            We are running Confluence 5.5.2 and Crowd 2.7.2, with Active Directory behind Crowd and sill encountering this issue. The ticket I had opened when I first encountered this issue, CSP-122249, was closed recognizing this as a bug. Are you saying we should open another ticket?

            IT Solutions Team added a comment - We are running Confluence 5.5.2 and Crowd 2.7.2, with Active Directory behind Crowd and sill encountering this issue. The ticket I had opened when I first encountered this issue, CSP-122249, was closed recognizing this as a bug. Are you saying we should open another ticket?

            We are using Confluence 5.3 and Crowd 2.7.2. I have raised a support ticket in the past, CSP126449, and was told it wasn't a bug.

            Crowd itself is integrated with an AD instance, rather than managing the user base directly.

            David Sorenson added a comment - We are using Confluence 5.3 and Crowd 2.7.2. I have raised a support ticket in the past, CSP126449, and was told it wasn't a bug. Crowd itself is integrated with an AD instance, rather than managing the user base directly.

            david.sorenson is you are using Crowd 2.7 or greater and Confluence 5.3 or greater then detecting user renames should work automatically. I suppose one other consideration is whether Crowd is managing the user base directly or itself integrated with remote directories?

            Assuming you are on matching versions of Confluence and Crowd then it would be worthwhile raising a support ticket so we can try to get to the bottom of this problem.

            Thanks.

            Paul Curren added a comment - david.sorenson is you are using Crowd 2.7 or greater and Confluence 5.3 or greater then detecting user renames should work automatically. I suppose one other consideration is whether Crowd is managing the user base directly or itself integrated with remote directories? Assuming you are on matching versions of Confluence and Crowd then it would be worthwhile raising a support ticket so we can try to get to the bottom of this problem. Thanks.

              Unassigned Unassigned
              tcomasseto Tiago Comasseto
              Affected customers:
              53 This affects my team
              Watchers:
              71 Start watching this issue

                Created:
                Updated:
                Resolved: