-
Suggestion
-
Resolution: Fixed
-
None
-
None
Atlassian status as of 31 Jan 2019
Hi everyone,
Bulk import of users and groups from an external system is supported via the new User provisioning (SCIM) API. We're pleased to announce that documentation for the API is now available on developer.atlassian.com. The API is an implementation of the SCIM specification and is intended to be used to sync users and groups from an identity provider to an Atlassian organization. Once you have linked an Atlassian Cloud site (like example.atlassian.net) to your organization, users and groups will be synced to your site and you can use them to control access to Jira and Confluence Cloud as well as permissions within those products. Learn more about how automatic user provisioning works with Atlassian Cloud.
There are several key benefits to automating user provisioning for Atlassian Cloud:
- It saves you time as an administrator by automating the process of creating and removing Atlassian accounts for your users
- It improves security by reducing errors in the provisioning/deprovisioning process
- It can help reduce costs by ensuring you are not billed for users who are no longer active
The SCIM API is intended for customers who are not already using one of our supported identity providers. We currently support Okta and are actively working on support for Azure Active Directory and Onelogin. If you are using one of these identity providers, we recommend using the supported Atlassian app for these identity providers as this will simplify the configuration process.
Regards,
Dave Meyer
Atlassian Access Product Management
Problem Definition
With the new Identity Platform for Cloud instances, it is not possible to bulk import users.
Suggested Solution
Create a Bulk User import Tool for either Atlassian Support or for end user to import a list of users via CSV
Why this is important
- This is a problem when migrating from JIRA Server to JIRA Cloud. External Directories are not support in JIRA Cloud. Users will need to be added manually
- Helpful feature for customers that wish to import all existing users into a new Cloud instance
- Key problem when attempting to merge two sets of users from Cloud instances (Cloud-to-Cloud merger)
Workaround
No workaround
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[ID-6376] Create tool for Bulk Importing Users into Cloud
| Workflow | Original: JAC Suggestion Workflow [ 3258606 ] | New: JAC Suggestion Workflow 3 [ 3644781 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: ACCESS Suggestion workflow [ 3156651 ] | New: JAC Suggestion Workflow [ 3258606 ] |
| Workflow | Original: reviewflow [ 2405190 ] | New: ACCESS Suggestion workflow [ 3156651 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Verified [ 10005 ] | New: Resolved [ 5 ] |
| Description |
Original:
{panel:title=Atlassian status as of 31 Jan 2019|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#4C9AFF|bgColor=#DEEBFF}
h3. Problem Definition With the new Identity Platform for Cloud instances, it is not possible to bulk import users. h3. Suggested Solution Create a Bulk User import Tool for either Atlassian Support or for end user to import a list of users via CSV h3. Why this is important * This is a problem when migrating from JIRA Server to JIRA Cloud. External Directories are not support in JIRA Cloud. Users will need to be added manually * Helpful feature for customers that wish to import all existing users into a new Cloud instance * Key problem when attempting to merge two sets of users from Cloud instances (Cloud-to-Cloud merger) h3. Workaround No workaround |
New:
{panel:title=Atlassian status as of 31 Jan 2019|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#4C9AFF|bgColor=#DEEBFF}
Hi everyone, Bulk import of users and groups from an external system is supported via the new User provisioning (SCIM) API. We're pleased to announce that documentation for the [API is now available on developer.atlassian.com|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/]. The API is an implementation of the [SCIM specification|http://www.simplecloud.info/] and is intended to be used to sync users and groups from an identity provider to an [Atlassian organization|https://confluence.atlassian.com/cloud/set-up-an-atlassian-organization-938859734.html]. Once you have linked an Atlassian Cloud site (like example.atlassian.net) to your organization, users and groups will be synced to your site and you can use them to control access to Jira and Confluence Cloud as well as permissions within those products. [Learn more about how automatic user provisioning works with Atlassian Cloud|https://confluence.atlassian.com/cloud/user-provisioning-959305316.html]. There are several key benefits to automating user provisioning for Atlassian Cloud: * It saves you time as an administrator by automating the process of creating and removing Atlassian accounts for your users * It improves security by reducing errors in the provisioning/deprovisioning process * It can help reduce costs by ensuring you are not billed for users who are no longer active The SCIM API is intended for customers who are not already using one of our supported identity providers. [We currently support *Okta*|https://confluence.atlassian.com/cloud/configure-user-provisioning-with-okta-957492956.html] and are actively working on support for *Azure Active Directory* and *Onelogin*. If you are using one of these identity providers, we recommend using the supported Atlassian app for these identity providers as this will simplify the configuration process. Regards, Dave Meyer Atlassian Access Product Management {panel} h3. Problem Definition With the new Identity Platform for Cloud instances, it is not possible to bulk import users. h3. Suggested Solution Create a Bulk User import Tool for either Atlassian Support or for end user to import a list of users via CSV h3. Why this is important * This is a problem when migrating from JIRA Server to JIRA Cloud. External Directories are not support in JIRA Cloud. Users will need to be added manually * Helpful feature for customers that wish to import all existing users into a new Cloud instance * Key problem when attempting to merge two sets of users from Cloud instances (Cloud-to-Cloud merger) h3. Workaround No workaround |
| Description |
Original:
h3. Problem Definition
With the new Identity Platform for Cloud instances, it is not possible to bulk import users. h3. Suggested Solution Create a Bulk User import Tool for either Atlassian Support or for end user to import a list of users via CSV h3. Why this is important * This is a problem when migrating from JIRA Server to JIRA Cloud. External Directories are not support in JIRA Cloud. Users will need to be added manually * Helpful feature for customers that wish to import all existing users into a new Cloud instance * Key problem when attempting to merge two sets of users from Cloud instances (Cloud-to-Cloud merger) h3. Workaround No workaround |
New:
{panel:title=Atlassian status as of 31 Jan 2019|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#4C9AFF|bgColor=#DEEBFF}
h3. Problem Definition With the new Identity Platform for Cloud instances, it is not possible to bulk import users. h3. Suggested Solution Create a Bulk User import Tool for either Atlassian Support or for end user to import a list of users via CSV h3. Why this is important * This is a problem when migrating from JIRA Server to JIRA Cloud. External Directories are not support in JIRA Cloud. Users will need to be added manually * Helpful feature for customers that wish to import all existing users into a new Cloud instance * Key problem when attempting to merge two sets of users from Cloud instances (Cloud-to-Cloud merger) h3. Workaround No workaround |
| Remote Link | New: This issue links to "Page (Extranet)" [ 369922 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 340172 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 339460 ] |
| Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |