Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-564

Allow multiple Identity Provider Entity IDs values in SAML configuration



    • 116
    • 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 Definition

      Currently, there's no way to add more than one Identity Provider Entity ID in Atlassian Access's SAML configuration.
      This turns IdP initiated logins impossible for more than one instance since most Identity Providers don't have the possibility to use the same Entity ID in more than one App on the provider side.

      Suggested Solution

      Add the ability to set multiple Identity Providers Entity IDs so that customers can set multiple apps at the Provider side, one for each of their instances.


      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


        Issue Links



              bmagro Ben Magro
              akasper André K. (Inactive)
              119 Vote for this issue
              94 Start watching this issue