Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-608

SCIM user provisioning: Allow the Organization's directory to pull groups from the integrated Cloud sites

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update 8/17/2020

      Hi everyone,

      My team and I have been working on the ability to connect your existing cloud site groups with you IDP groups. We are happy to announce that we shipped this capability today to all customers. Here is a description of how this feature works https://confluence.atlassian.com/cloud/resolve-group-conflicts-before-syncing-users-1014677306.html .

      Thanks for voting and commenting on this issue. Your feedback has been incredibly helpful to our team as we’ve worked on bringing this feature to you.

      Cheers!

      Narmada Jayasankar

      Product Manager, Atlassian Access

      njayasankar@atlassian.com

       

       

      SCIM user provisioning: Allow the Organization's directory to pull groups from the integrated Cloud sites in order to use these same groups for management on the Identity Provider.

      For Okta

      This would allow Okta to pull the same groups from Atlassian to link with its own groups of users, instead of pushing new groups to a Cloud site to be re-configured on permission level and memberships.

      For other IDPs

      It would depend on how the Identity Provider handles groups and SCIM integrations.

            [ACCESS-608] SCIM user provisioning: Allow the Organization's directory to pull groups from the integrated Cloud sites

            Italo Qualisoni [e-Core] added a comment - - edited

            This is important in cases of Server to Cloud migration, we have a customer that used to have LDAP sync in server and now after moving to the cloud we are having this limitation to enable the user provisioning to sync the groups.

            Italo Qualisoni [e-Core] added a comment - - edited This is important in cases of Server to Cloud migration, we have a customer that used to have LDAP sync in server and now after moving to the cloud we are having this limitation to enable the user provisioning to sync the groups.

            Simi S added a comment -

            Hi everyone,

            Thanks for your feedback on this issue. We’re currently investigating some improvements to user provisioning to help customers with this issue, and we now have design prototypes. 

            If you can spare 30 minutes to chat with me about this over video call or provide feedback over email, email me at sshaheed@atlassian.com to let me know you’re interested in providing some feedback on the draft designs!

            Thanks!

            Simi
            Designer, Atlassian

            Simi S added a comment - Hi everyone, Thanks for your feedback on this issue. We’re currently investigating some improvements to user provisioning to help customers with this issue, and we now have design prototypes.  If you can spare 30 minutes to chat with me about this over video call or provide feedback over email, email me at sshaheed@atlassian.com to let me know you’re interested in providing some feedback on the draft designs! Thanks! Simi Designer, Atlassian

            Alex Zia added a comment -

            Can't you simply allow add provisioned groups into already existent groups?  (like nested groups we used to have in Jira Server, befor Jira Cloud)

            This way we could create new idp provisioned groups, and add the new groups into pre existant groups, so no need to change the permissions in projects

            Alex Zia added a comment - Can't you simply allow add provisioned groups into already existent groups?  (like nested groups we used to have in Jira Server, befor Jira Cloud) This way we could create new idp provisioned groups, and add the new groups into pre existant groups, so no need to change the permissions in projects

            Alex Zia added a comment -

            This is High priority to us, we have over 1200 already existant accounts and over 100 already existant projects.

            All our projects permissions are based in these existant groups.

            Atlassian Access with SCIM provisioning Is a no-go for us if we would have to create new groups and edit all our projects to redefine permissions based on new groups.

             

             

            Alex Zia added a comment - This is High priority to us, we have over 1200 already existant accounts and over 100 already existant projects. All our projects permissions are based in these existant groups. Atlassian Access with SCIM provisioning Is a no-go for us if we would have to create new groups and edit all our projects to redefine permissions based on new groups.    

              njayasankar@atlassian.com Narmada Jayasankar
              rbecker Rodrigo B.
              Votes:
              25 Vote for this issue
              Watchers:
              33 Start watching this issue

                Created:
                Updated:
                Resolved: