Jira OAuth Single-Sign On(SSO) for Atlassian Cloud allows you to securely login using Github credentials. Single Sign-on (SSO) into your Atlassian Access or Atlassian Jira Cloud Account with any of your existing OAuth Provider credentials for enhanced security using our module.
Atlassian Guard is an additional subscription applied across the Atlassian Cloud products like Jira Software, Jira Service Management, Jira Work Management, Confluence, and Bitbucket. It is needed for Single Sign-On (SSO) or any Cloud Service that comes under Atlassian Guard.
The first step of Atlassian Guard starts with the Domain Verification process to enforce 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 Github as IDP
Part 1 + Part 2 : Testing SSO between Atlassian cloud as SP and Github 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 |
Obtain the following steps to get callback url.
IdP Name | Custom Provider |
IdP Display Name | Choose appropriate Name |
OAuth Authorize Endpoint | https://{Github-app-domain}/oauth2/authorize | OAuth Access Token Endpoint | https://{Github-app-domain}/oauth2/token | OAuth Get User Info Endpoint (optional) | https://{Github-app-domain}/oauth2/userInfo |
Client ID | This value can be obtained from the above steps |
Client secret | This value can be obtained from the above steps |
Scope | openid |