-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
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
- Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers.
- Attempt to configure SSO settings for individual projects.
- 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
- mentioned in
-
Page Failed to load
[ACCESS-2219] Ability to configure SSO on a per-project basis in JSM for Portal-Only Customers.
| Support reference count | Original: 1 | New: 2 |
| Support reference count | New: 1 |
| Remote Link | New: This issue links to "Page (Confluence)" [ 1004176 ] |
| Security | Original: Atlassian Staff [ 10750 ] |
| Description |
Original:
h2. Summary
The customer is seeking to implement 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 the customer due to varying requirements across different clients. They are looking for a solution that allows SSO settings to be distinguished at a project or portal level. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. Technical Details * Feature request reference: ACCESS1952 - Allow Multiple External User Security (EUS) Policies. * 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. h2. Additional Context The customer has multiple projects with portal-enabled settings and is facing challenges in managing SSO across different clients. They have expressed that the current workaround of creating multiple organizations is not a viable solution for their needs. h2. Please help with * Can we explore the feasibility having this new feature request for implementing SSO on a per-project basis in JSM? |
New:
h2. 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. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. 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. h2. Please help with * Explore the feasibility of implementing SSO on a per-project basis in JSM |
| Description |
Original:
h2. Summary
The customer is seeking to implement 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 the customer due to varying requirements across different clients. They are looking for a solution that allows SSO settings to be distinguished at a project or portal level. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. Technical Details * Feature request reference: ACCESS1952 - Allow Multiple External User Security (EUS) Policies. * 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. h2. Additional Context The customer has multiple projects with portal-enabled settings and is facing challenges in managing SSO across different clients. They have expressed that the current workaround of creating multiple organizations is not a viable solution for their needs. h2. Please help with * Can we explore the feasibility of creating a new feature request for implementing SSO on a per-project basis in JSM? * What additional information or requirements do we need from the customer to support the feature request effectively? |
New:
h2. Summary
The customer is seeking to implement 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 the customer due to varying requirements across different clients. They are looking for a solution that allows SSO settings to be distinguished at a project or portal level. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. Technical Details * Feature request reference: ACCESS1952 - Allow Multiple External User Security (EUS) Policies. * 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. h2. Additional Context The customer has multiple projects with portal-enabled settings and is facing challenges in managing SSO across different clients. They have expressed that the current workaround of creating multiple organizations is not a viable solution for their needs. h2. Please help with * Can we explore the feasibility having this new feature request for implementing SSO on a per-project basis in JSM? |
| Summary | Original: Ability to configure SSO for specific customer organizations in JSM for Portal-Only Customers. | New: Ability to configure SSO on a per-project basis in JSM for Portal-Only Customers. |
| Description |
Original:
h2. Summary
The customer is seeking to implement 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 the customer due to varying requirements across different clients. They are looking for a solution that allows SSO settings to be distinguished at a project or portal level. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. Technical Details * Feature request reference: ACCESS1952 - Allow Multiple External User Security (EUS) Policies. * 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. h2. Additional Context The customer has multiple projects with portal-enabled settings and is facing challenges in managing SSO across different clients. They have expressed that the current workaround of creating multiple organizations is not a viable solution for their needs. h2. Please help with * Can we explore the feasibility of creating a new feature request for implementing SSO on a per-project basis in JSM? * What additional information or requirements do we need from the customer to support the feature request effectively? |
New:
h2. Summary
The customer is seeking to implement 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 the customer due to varying requirements across different clients. They are looking for a solution that allows SSO settings to be distinguished at a project or portal level. h2. How to Replicate # Access the Jira Service Management (JSM) instance with multiple projects enabled for portal customers. # Attempt to configure SSO settings for individual projects. # Observe that the SSO setting applies universally to all portal customers rather than on a per-project basis. h2. Technical Details * Feature request reference: ACCESS1952 - Allow Multiple External User Security (EUS) Policies. * 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. h2. Additional Context The customer has multiple projects with portal-enabled settings and is facing challenges in managing SSO across different clients. They have expressed that the current workaround of creating multiple organizations is not a viable solution for their needs. h2. Please help with * Can we explore the feasibility of creating a new feature request for implementing SSO on a per-project basis in JSM? * What additional information or requirements do we need from the customer to support the feature request effectively? |