Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-24887

Provide a path to migrate user information from Crowd to JIRA during the upgrade to version with Crowd Embeded

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Won't Do
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Crowd Embedded was introduce in JIRA 4.3.x making the full integration with LDAP now available in the JIRA install itself, avoiding the need of integration with a external Crowd instance. In other hand, during a upgrade from previous version to JIRA 4.3.x if users management was once delegated to external Crowd and this integration is removed, users are not migrated to JIRA internal user database.

      Atlassian does not provide a path to migrate user information from Crowd to JIRA during the upgrade. This is by design. If you previous installation of JIRA was integrated with Crowd, all users, groups and membership information will be saved on Crowd database. Therefore if during the upgrade the external instance of Crowd is not available or if upgrade notes for Crowd integrated were not follow, JIRA will NOT recreate the users locally.

      Workaround: http://confluence.atlassian.com/display/JIRAKB/Migration+path+from+Crowd+to+Crowd+Embedded+during+upgrade+to+JIRA+4.3.x

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mspindler MorganaA
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: