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

Have the option to configure SAML at instance level rather than at organization level

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.

      Problem Definition

      When a customer has several separate Cloud instances with different URLs on the same domain, they cannot create and link two separate applications within their Identity Provider as the Entity Provider URL is configured at organization level and not at instance level. Each of the separate applications will have a separate Entity Provider URL.

      This disrupts the Identity Provider initatiated workflow as it doesn't allow the customer to create separate applications for each of the instances and manage separately the access to those aplications.

      Suggested Solution

      Have the option to configure SAML separately by instance rather than by Organization or Domain.

      Workaround (Optional) 

      When users log in via the Cloud instance URL (Service Provider initiated workflow) the users can still access.

            [ACCESS-37] Have the option to configure SAML at instance level rather than at organization level

            Rob Saunders made changes -
            Comment [ Thank you for such important and essential tips, I will surely follow your guidelines to increase the traffic to my website. Increasing the traffic for your website is a very difficult task and you can get help from [college essay writers|https://collegessaywriters.com/] to solve your problems easily. I respect you for helping people. ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3332667 ] New: JAC Suggestion Workflow 3 [ 3588263 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Shawn C made changes -
            Link New: This issue is related to ACCESS-605 [ ACCESS-605 ]
            Michael Andreacchio made changes -
            Workflow Original: ACCESS Suggestion workflow [ 3156128 ] New: JAC Suggestion Workflow [ 3332667 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Rob Saunders made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 438801 ]
            Katherine Yabut made changes -
            Workflow Original: reviewflow [ 2487799 ] New: ACCESS Suggestion workflow [ 3156128 ]
            lingbo (Inactive) made changes -
            Component/s New: SAML [ 53303 ]
            Dave Meyer made changes -
            Link New: This issue is superseded by ACCESS-572 [ ACCESS-572 ]

            mchyzer2 added a comment -

            We have a large organization (upenn.edu) and we want SSO for our IT department site.  But if an alumni or a staff member in another school uses their whatever@upenn.edu email account, why should we have to pay an IAM fee?  There should be a solution to this use case.  Thanks, Chris

            mchyzer2 added a comment - We have a large organization (upenn.edu) and we want SSO for our IT department site.  But if an alumni or a staff member in another school uses their whatever@upenn.edu  email account, why should we have to pay an IAM fee?  There should be a solution to this use case.  Thanks, Chris
            Dave Meyer made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 379109 ]

              Unassigned Unassigned
              malonso@atlassian.com Miguel Alonso
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: