Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-653

Migrating from Atlassian Server products where SCIM was enabled to Atlassian Cloud and then using Atlassian Access SCIM causes users to be given GUID usernames

    XMLWordPrintable

    Details

      Description

      Summary

      Migrating from Atlassian Server products where SCIM was enabled to Atlassian Cloud and then using Atlassian Access SCIM causes users to be given GUID (or UUID) usernames.

      Steps to Reproduce

      1. Have a Jira/Confluence server setup connected to an IDP for SCIM.
      2. Migrate from Server to Cloud using Jira site import.
      3. Enable Atlassian Access & SCIM in new Cloud site

      Expected Results

      SCIM will be enabled and users will sync to the IDP and retain their configuration as they did in cloud.

      Actual Results

      Some users are issued new usernames in the form of UUID's, this breaks the connection to all their historic work done in the server instance.

      Notes

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gvenkatesh@atlassian.com Gautam Venkatesh
              Reporter:
              nwolfgang Battlebeard (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              48 Start watching this issue

                Dates

                Created:
                Updated: