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

      User Problem

      External Users can be required sign in through an org controlled SSO, but these users are billable.
      See Available external user security policy and settings

      Not all external users are equally trusted. So it should be possible to have multiple groups of External Users and require most to undergo the security step up, but others if you know they belong to a trusted organisation or domain should be able to bypass this step up.

      Suggested Solutions

      Enable a multiple external user security policy or implement add conditions to apply the security policy.

      Current Workarounds

      None

            [ACCESS-1952] Allow Multiple External User Security Policies

            SET Analytics Bot made changes -
            Support reference count Original: 35 New: 36
            Sudesh Peram made changes -
            Status Original: Gathering Interest [ 11772 ] New: Under Consideration [ 11774 ]

            John P Dion added a comment -

            Similar to others, we have 400 external users, each with different IDP's(Entra, Google, none) so I need the ability to push certain external users to a policy that they can utilize and the rest into OTP.  If I'm forced to choose I currently only can setup OTP.  This needs action.

            John P Dion added a comment - Similar to others, we have 400 external users, each with different IDP's(Entra, Google, none) so I need the ability to push certain external users to a policy that they can utilize and the rest into OTP.  If I'm forced to choose I currently only can setup OTP.  This needs action.
            SET Analytics Bot made changes -
            Support reference count Original: 34 New: 35
            SET Analytics Bot made changes -
            Support reference count Original: 33 New: 34

            grab added a comment -

            We need this urgent too and have been waiting since month for a solution. I don't know why Atlassian implemented it so badly by only leaving one option?

            grab added a comment - We need this urgent too and have been waiting since month for a solution. I don't know why Atlassian implemented it so badly by only leaving one option?

            We are an enterprise sized organization. We provide services to similar enterprise sized organizations. We would like to cooperate with them in Jira for ticketing.

            Currently we cannot have SSO setup for our different customers, as one IDP has to be chosen for all external users. 

            If we setup SSO, and even one of our customer is unable / unwilling to use it, we cannot onboard them to JIRA.

            Atlassian advertise its products with huge efficiency gain. If we cannot use Federated Identity Management and manually has to manage hundreds of users, we won't see any gain. This functionality is not adequate on enterprise level.

            For each IDP we should be able to set SSO / OTP separately or a setting that the SSO is provided by the IDP the user is provisioned from.

            Marcell Bendik added a comment - We are an enterprise sized organization. We provide services to similar enterprise sized organizations. We would like to cooperate with them in Jira for ticketing. Currently we cannot have SSO setup for our different customers, as one IDP has to be chosen for all external users.  If we setup SSO, and even one of our customer is unable / unwilling to use it, we cannot onboard them to JIRA. Atlassian advertise its products with huge efficiency gain. If we cannot use Federated Identity Management and manually has to manage hundreds of users, we won't see any gain. This functionality is not adequate on enterprise level. For each IDP we should be able to set SSO / OTP separately or a setting that the SSO is provided by the IDP the user is provisioned from.
            SET Analytics Bot made changes -
            Support reference count Original: 32 New: 33
            Tyler B [Atlassian] made changes -
            Remote Link Original: This issue links to "ENT-3121 (Jira)" [ 1025768 ] New: This issue links to "ENT-3121 (Hello Jira)" [ 1025768 ]
            SET Analytics Bot made changes -
            Support reference count Original: 31 New: 32

              e902c0832f88 Sudesh Peram
              5f7be16d2f76 Andrew Delaney
              Votes:
              73 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated: