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

Ability to configure SSO on a per-project basis in JSM for Portal-Only Customers.

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

      Summary

      Customers are interested in implementing Single Sign-On (SSO) specifically for Portal Only Customers in Jira Service Management (JSM) on a per-project basis. Currently, SSO can only be enabled across all portal customers, which is not feasible for some setups due to varying requirements across different clients. Creating multiple organizations may not always be a viable solution.
      It would be good to have a solution which allows SSO settings to be distinguished at a project or portal level.

      How to Replicate

      1. Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers.
      2. Attempt to configure SSO settings for individual projects.
      3. Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis.

      Technical Details

      • Current limitation: SSO can only be enabled for all portal customers or none.
      • Customer's requirement: SSO to be applied selectively for individual customer organizations within different projects.

      Please help with

      • Explore the feasibility of implementing SSO on a per-project basis in JSM

            [ACCESS-2219] Ability to configure SSO on a per-project basis in JSM for Portal-Only Customers.

              Unassigned Unassigned
              c793a29d3066 Praveen Gatakala
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: