Complete Guide to Atlassian Cloud SSO (Single Sign-On) Using Okta as OAuth Provider

Atlassian Cloud OAuth Single Sign-On (SSO) with Okta

With Jira OAuth Single Sign-On (SSO) for Atlassian Cloud, you can securely log in to Atlassian Cloud using your Okta credentials. This app allows you to implement seamless Single Sign-On (SSO) for Atlassian Cloud accounts using existing Okta credentials.

Pre-requisites

  1. Atlassian Guard (Atlassian Access) Subscription:
    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 across Atlassian Cloud products.
  2. Domain Verification:
    An essential step to enforce SSO on managed user accounts through Atlassian Guard is Domain Verification. This process verifies that your organization has a valid domain for managing the user accounts and uses the same domain name for the email addresses.

Download and Installation

  • Log in to your Atlassian Admin Console and select your site.
  • Now, in the left sidebar, scroll down to the Apps section. Under Apps, select Site, which will open the site settings page.
  • In the site settings, navigate to Connected Apps → Explore apps. (Alternatively, you can go to the Atlassian Marketplace and search for the app.)
  • Search for miniOrange OAuth/OpenID SSO.
  • Click “Try it Free” to begin a new trial of the app.
  • Now, in the top menu bar, go to Apps.
  • Locate the “mO Jira OAuth/OpenID SSO” app and click to open it.

In this guide, we will demonstrate the setup in three parts:

  1. Configure OAuth SSO connection between miniOrange App (as OAuth Client) and Okta (as OAuth Provider).
  2. Configure SAML SSO connection between Atlassian Guard (as SP) and miniOrange App (as IDP).
  3. Add users to the SSO Authentication policy, and enforce the SSO.

Step 1. Configure SSO connection between miniOrange App and Okta

  • Once the plugin is installed, select the Apps section from the sidebar menu and click on the mO Jira OAuth/OIDC SSO.
  • Jira app main menu with the Apps section open and the mO Jira OAuth/OIDC SSO app highlighted
  • Next, you will be prompted with a welcome pop-up window. Click Start Configuration.
  • Welcome window of mO Jira OAuth/OIDC SSO app.
  • Now, in the Configured Providers section, click the "Add Provider" button.
  • Configured providers section in the mO Jira OAuth/OIDC SSO app
  • Select Okta as the OAuth provider.
  • Copy the callback URL from the OAuth / OIDC Provider Configurations page and keep it handy, as you'll need it to configure Okta as the OAuth provider.
  • OAuth / OIDC Provider Configurations tab in the mO Jira OAuth/OIDC SSO app
  • After copying the callback URL, navigate to the Okta admin dashboard and click on ApplicationsCreate App Integration.
  • On Okta admin Dashboard side menu Application section with Create App Integration button highlighted.
  • Here, choose OIDC - OpenID Connect as a Sign-in method, select Web Application as the Application type, and click Next.
  • New app integration page in Okta admin dashboard with OIDC - OpenID Connect as a Sign-in method and Web Application as the Application type selected.
  • Now, enter the App Integration Name and Callback URL in the Sign-in redirect URIs, and proceed with the OAuth app configuration.
  • Okta's new app general setting where the user provides the app name and Callback URL
  • Copy the Client ID and Client Secret.
  • Okta new application general tab from where Client ID and Client Secret can be copied
  • Then go to the Security → API page from the Okta dashboard.
  • Under the Authorization Servers tab select the default server.
  • Okta admin dashboard side menu API section where default Authorization server configuration can be found
  • Then click on the link given in the Metadata URI field.
  • Okta admin dashboard settings page where Metadata URI can be found
  • Copy the Authorization endpoint, Token endpoint, etc., and keep it handy.
  • Now, return to the miniOrange App configuration page. (OAuth / OIDC Provider Configurations)
  • Enter the Client ID, Client Secret, Okta Domain URL, and required scopes, such as openid, email, and profile, and click Save Configuration.
  • Pro Tip: You can find your Okta domain by clicking on your username in the top-right corner of the Admin Console. The domain will be displayed in the dropdown menu.
  • mO Jira OAuth/OIDC SSO app configuration page where Client ID, Client Secret, Scopes, and other required endpoints can be entered

Step 2. Set up SSO between Atlassian Guard and miniOrange App

After saving the OAuth Configuration, you’ll be required to configure Atlassian Guard and the miniOrange OAuth/OIDC SSO App.

  • A pop-up notification will appear, asking you to complete the Atlassian Guard configuration.
  • Pop-up notification asking to complete the Atlassian Guard configuration
  • Click on Configure Guard, and you will be navigated to the Guard Configurations section.
  • In this section, you will find the Plugin Metadata details.
  • Copy and keep the following values handy. You’ll need them while setting up your Identity Provider in Atlassian Guard:
    • IDP Entity ID
    • IDP SSO URL
    • IDP Public X.509 Certificate
    • Atlassian Guard configurations page where Plugin Metadata details can be found
    1. Open the Atlassian Admin Console and navigate to the Security tab.
    2. Note: In case you manage multiple organizations, you’ll have to select the intended one after accessing the admin console.
    3. Under User Security, click Identity Providers.
    4. Select Other to begin configuring a custom Identity Provider.
    5. Atlassian Guard security page where Identity Providers section can be found
  • Provide an appropriate name, select Set up SAML Single Sign-On, and click Next.
  • Now, paste the IDP Entity ID, IDP SSO URL, and Public X.509 Certificate that you copied from the plugin configuration.
  • Atlassian Guard configurations page where IDP Entity ID, IDP SSO URL, and Public X.509 Certificate can be pasted
  • Click Next and copy the Service Provider Entity ID and Service Provider Assertion Consumer Service URL. Keep these handy as they’re required to complete the plugin configuration.
  • Complete the rest of the Atlassian Guard configuration.
  • Once you’re done, return to the plugin, go to the SP Metadata tab in the Guard Configurations section, and click Next.
  • Enter the SP Entity ID and Assertion Consumer Service (ACS) URL that you copied, and click Save Settings.
  • Atlassian Guard configurations page where SP Metadata tab can be found

Step 3: Configure SSO Authentication Policy

Once all the SSO Configurations are done, you need to add users to the Authentication Policy and enforce Single Sign On.

After saving the SP Metadata, click Next to find the steps for adding the users to the Authentication policy.

Atlassian Guard configurations page where Authentication Policy tab can be found

Now you can now seamlessly enjoy Single-Sign On into Atlassian with your preferred OAuth provider, with our miniOrange app.

OAuth Saml App

Did this page help you?

miniOrange Atlassian Contact Us

Book a Free Consultation with
Our Experts Today!

Schedule a call now!


Contact Us