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

Allow multiple Identity Provider(IdP) configurations for a single org and domain

XMLWordPrintable

    • 394

    • 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 an organization, which applies to all Atlassian accounts on any of that organization's verified domains. This poses a problem for organizations that are using multiple IdPs for users that share the same email domain or if an organization needs multiple SSO/provisioning configurations to support their use cases.

      Solution

      Provide a way for organizations to apply multiple SSO via SAML and/or provisioning(SCIM) configurations to different users on the same domain.

      Atlassian Update – 19th September 2022

      Hi everyone,

      This feature is now shipped in the Atlassian Cloud Enterprise Plan The documentation for this feature can be found here: https://support.atlassian.com/provisioning-users/docs/add-identity-providers-to-connect-users/

      We made the decision to not bundle security-related features in Standard and Premium product editions. This means customers on either standard or premium can purchase Access if they require our standard security features like SSO and Audit Logging.

      Anything that fits into the more Advance category of security features like Multiple Identity Providers will be packaged in our Enterprise edition as we believe this edition is the best fit for those customers.

      I know this is not ideal to hear for some customers, but the decision was not made lightly. 

      Ben Magro
      Product Manager, Cloud Security

            [ACCESS-572] Allow multiple Identity Provider(IdP) configurations for a single org and domain

            Ramon M made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 775801 ]
            Tatsuya Uekusa made changes -
            Link New: This issue relates to ACCESS-1526 [ ACCESS-1526 ]
            cmac made changes -
            Link New: This issue duplicates CLOUD-10619 [ CLOUD-10619 ]
            Sascha Wiswedel made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 640811 ]
            Jimmy Van made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 595503 ]
            Ben Magro (Inactive) made changes -
            Description Original: *Problem*

            Currently, Atlassian Access applies a single configuration to an Identity Provider(IdP) for an organization, which applies to all Atlassian accounts on any of that organization's verified domains. This poses a problem for organizations that are using multiple IdPs for users that share the same email domain or if an organization needs multiple SSO/provisioning configurations to support their use cases.

            *Solution*

            Provide a way for organizations to apply multiple SSO via SAML and/or provisioning(SCIM) configurations to different users on the same domain.             		New: *Problem*

            Currently, Atlassian Access applies a single configuration to an Identity Provider(IdP) for an organization, which applies to all Atlassian accounts on any of that organization's verified domains. This poses a problem for organizations that are using multiple IdPs for users that share the same email domain or if an organization needs multiple SSO/provisioning configurations to support their use cases.

            *Solution*

            Provide a way for organizations to apply multiple SSO via SAML and/or provisioning(SCIM) configurations to different users on the same domain.
            {panel:title=Atlassian Update – 19th September 2022|borderStyle=solid|borderColor=#ebf2f9|titleBGColor=#ebf2f9|bgColor=#ffffff}
            Hi everyone,

            This feature is now shipped in the [Atlassian Cloud Enterprise Plan|https://www.atlassian.com/enterprise/cloud/cloud-enterprise] The documentation for this feature can be found here: [https://support.atlassian.com/provisioning-users/docs/add-identity-providers-to-connect-users/]

            We made the decision to not bundle security-related features in Standard and Premium product editions. This means customers on either standard or premium can purchase Access if they require our standard security features like SSO and Audit Logging.

            Anything that fits into the more Advance category of security features like Multiple Identity Providers will be packaged in our Enterprise edition as we believe this edition is the best fit for those customers.

            I know this is not ideal to hear for some customers, but the decision was not made lightly. 

            Ben Magro
            Product Manager, Cloud Security
            {panel}
            SET Analytics Bot made changes -
            Support reference count Original: 393 New: 394
            Ben Magro (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            Support reference count Original: 392 New: 393
            SET Analytics Bot made changes -
            Support reference count Original: 391 New: 392

              bmagro Ben Magro (Inactive)
              dmeyer Dave Meyer
              Votes:
              284 Vote for this issue
              Watchers:
              270 Start watching this issue

                Created:
                Updated:
                Resolved: