We are happy to announce special offers for miniOrange Atlassian SSO, 2FA, REST API, User Sync and Group Sync Apps.
Jira SAML Single-Sign On(SSO) for Atlassian Cloud allows you to securely login using PingOne credentials. Single Sign-on (SSO) into your Atlassian Access or Atlassian Jira SAML Account with any of your existing Identity Provider credentials for enhanced security and features using our module.
Atlassian Access is an additional subscription applied across the Atlassian cloud products like Jira Software, Jira Service Management, Jira Work Management, Confluence, Bitbucket, etc. So it is needed for Single Sign-On(SSO) or any Cloud Service which comes under Atlassian Access.
The first step of Atlassian Access starts with the Domain Verification Process to enforce SAML SSO on the managed user accounts. This process verifies that you own a valid domain for managing the user accounts and use the same domain name for the email addresses.
In this document, we will demonstrate the setup in two parts.
Part 1: Configure SAML SSO between Atlassian cloud as SP and miniOrange as IDP
Part 2: Configure SAML SSO between miniOrange as SP and PingOne as IDP
Part 1 + Part 2 : Testing SSO between Atlassian cloud as SP and PingOne as IDP using miniOrange Identity Broker.
|Custom Application Name||Any name would be fine|
|SP Entity ID or Issuer||You will receive after configuring Atlassian Access App|
|ACS URL||You will receive after configuring Atlassian Access App|
Provide the SAML configuration details for the application.
You can also provide following optional attributes.
|IDP Entity ID||Entity ID of IDP|
|Single Login URL||Login Url from IDP|
|Single Logout URL||Logout Url from IDP|
|X.509 Certificate||The public key certificate of your IDP.|
|Domain Mapping||Can be used to redirect specific domain user to specific IDP|
|Show IdP to Users||Enable this if you want to show this IDP to all users during Login|
|Send Configured Attributes||Enabling this would allow you to add attributes to be sent from IDP|