-
Bug
-
Resolution: Fixed
-
High
-
192
-
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
- Have a Jira/Confluence server setup connected to an IDP for SCIM.
- Migrate from Server to Cloud using Jira site import.
- 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.
Workaround for Jira Site Import
- If you are performing Jira's Site Import for a migration / data restore and are worried about user's content getting unmapped due to this bug.
- Provision users via SCIM
- Then use the option "I've migrated user data using the Jira Cloud Migration Assistant" on the Restore System Screen and leave all users in the XML files that you are importing.
- The users content will be mapped correctly based on the email address as the common identifier.
- is blocked by
-
ACCESS-657 Support more attributes for user-provisioning
- Closed
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[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
| Remote Link | New: This issue links to "Page (Confluence)" [ 627862 ] |
| Description |
Original:
h3. 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. h3. Steps to Reproduce # Have a Jira/Confluence server setup connected to an IDP for SCIM. # Migrate from Server to Cloud using Jira site import. # Enable Atlassian Access & SCIM in new Cloud site h3. Expected Results SCIM will be enabled and users will sync to the IDP and retain their configuration as they did in cloud. h3. 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. h3. Notes h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. 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. h3. Steps to Reproduce # Have a Jira/Confluence server setup connected to an IDP for SCIM. # Migrate from Server to Cloud using Jira site import. # Enable Atlassian Access & SCIM in new Cloud site h3. Expected Results SCIM will be enabled and users will sync to the IDP and retain their configuration as they did in cloud. h3. 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. h3. Workaround for Jira Site Import * If you are performing Jira's Site Import for a migration / data restore and are worried about user's content getting unmapped due to this bug. * Provision users via SCIM * Then use the option "{*}+I've migrated user data using the Jira Cloud Migration Assistant+{*}" on the Restore System Screen and leave all users in the XML files that you are importing. * The users content will be mapped correctly based on the email address as the common identifier. |
| Remote Link | New: This issue links to "Page (Confluence)" [ 603360 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Support reference count | Original: 191 | New: 192 |
| Support reference count | Original: 190 | New: 191 |
| Support reference count | Original: 189 | New: 190 |
| Support reference count | Original: 188 | New: 189 |
| Support reference count | Original: 189 | New: 188 |
| Support reference count | Original: 190 | New: 189 |