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

Allow non-enterprise customers to temporarily have multiple IDPs

XMLWordPrintable

    • 114

    • 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.

      Problem

      Currently, Atlassian Access applies a single configuration to an Identity Provider(IdP) for non-enterprise customers.

      Enterprise customers received the feature to have multiple IDPs configured. But non-enterprise customers have a serious problem when they are looking to migrate from one IDP to another as they need to wipe out their current working IDP configuration to configure the new one.

      This poses a problem for organizations as they need to take extra caution before proceeding, including accounting for prolonged user downtime, more communications to be sent information about the changes, and also more lengthy change windows.

       

      Solution

      Provide a way for non-enterprise customers to enable multiple IDPs temporarily, allowing them to test the configuration of the new IDP without having to delete the IDP that is already working.

       

      Update - August 2023

      On August 2023, a new feature was released by the development team to allow non-enterprise Access customers to create a second IdP without the need for an Enterprise Subscription or Enterprise Override.

      Two new operations have been made available for Support engineers that will enable an org to create the second IdP (directory) for 30 days, and updated to up to 60 days.

      Please note that this feature is still in the experimental phase, but customers that want to enable this feature to temporarily have a second IdP configured can raise a support ticket for Atlassian requesting it.

       

            [ACCESS-1526] Allow non-enterprise customers to temporarily have multiple IDPs

            David Osteso Pardo added a comment -

            Hi Atlassian!

            At the end there is some reliable solution for this limitation, it is not clear to me if the proposed solution is applicable or not.

            Thanks!

             

            David Osteso Pardo added a comment - Hi Atlassian! At the end there is some reliable solution for this limitation, it is not clear to me if the proposed solution is applicable or not. Thanks!  

            Dusty Brossart added a comment -

            We are in need of this feature for merging with our sister company, so that we can have their IdP connected during the migration/transition. We only have the 201-300 plan and have no need to upgrade to enterprise, so having a secondary IdP temporarily while we migrate would be fantastic and will make the migration much less complicated.

            Dusty Brossart added a comment - We are in need of this feature for merging with our sister company, so that we can have their IdP connected during the migration/transition. We only have the 201-300 plan and have no need to upgrade to enterprise, so having a secondary IdP temporarily while we migrate would be fantastic and will make the migration much less complicated.

            Joabe Soares added a comment -

            https://getsupport.atlassian.com/browse/PCS-203294

            Joabe Soares added a comment - https://getsupport.atlassian.com/browse/PCS-203294

            John Sears added a comment -

            Our use case: we have 1 IDP for SSO.

            -We are managing all groups and users inside Atlassian Access.

            We are needing another IDP for group/user provisioning, to connect to our Azure environment. Probably would use it for "mini-orange usersync".

             

            However, we only have 300 Active Atlassian Users.

            John Sears added a comment - Our use case: we have 1 IDP for SSO. -We are managing all groups and users inside Atlassian Access. We are needing another IDP for group/user provisioning, to connect to our Azure environment. Probably would use it for "mini-orange usersync".   However, we only have 300 Active Atlassian Users.

              e902c0832f88 Sudesh Peram
              e2c560fcca76 Giovani Cruzara [Atlassian]
              Votes:
              21 Vote for this issue
              Watchers:
              44 Start watching this issue

                Created:
                Updated: