Business Challenge
Atlassian’s native authentication for Jira Service Management (JSM) supports SAML-based Single Sign-On (SSO); however, Atlassian Guard does not support multiple SAML identity providers (IDPs) in its default offering. This limitation poses a challenge for organizations that need to authenticate users across multiple providers or business units, restricting flexibility in access management.
Solution Overview
Our SAML/OAuth SSO for JSM Customers eliminates this restriction, allowing organizations to seamlessly integrate multiple SAML IDPs—all without requiring Atlassian Guard or an Enterprise plan.
Key Benefits
Connect multiple IDPs with SAML and auto-redirect users based on email domains.
Connect Multiple IDPs with SAML
Admins can configure multiple Identity Providers (IDPs) simultaneously. Supported IDPs include: SAML-based IDPs: Okta, OneLogin, PingFederate, Azure AD (Entra ID), AWS, Keycloak, Oracle, Salesforce, etc.
Flexible Authentication Options
Once the IDP setup is complete, users can authenticate via the links. If multiple IDPs are configured, users will be redirected to the IDP selection page.
Automatic IDP Redirection Rules
For a streamlined user experience, admins can enforce redirection rules based on email domains using our in-house broker solution. Instead of displaying the IDP selection page, users will be redirected automatically to their assigned IDP.
Conclusion
Enable secure and scalable authentication for external users in Jira Service Management without relying on Atlassian Guard or an Enterprise plan. Our solution supports easy configuration of multiple SAML/OAuth IDPs and offers seamless user experiences through domain-based redirection rules. This allows organizations to manage access across different business units or partners while maintaining flexibility, security, and simplicity in the login process.
