You are viewing the Kantega SSO legacy documentation. The new documentation site is:
Skip to end of metadata
Go to start of metadata

Relatert bilde

Setup guide for adding Auth0 login to Atlassian server and datacenter products.

Context: This setup guides assumes that Kantega SSO in installed as an add-on to your Atlassian product (JiraConfluenceBitbucketBamboo, or FeCru).

The setup starts in the Configuration page of the Kantega SSO add-on. This configuration page can be found by pressing "Configure" on "Kantega Single Sign-On (SSO)" in list of installed add-ons.

1: Click “Add SAML identity provider" and select “Auth0


Copy the ACS URL/ Entity ID (the URLs are identical). They are used in a later step

Add a new Client

In Auth0 navigate to Dashboard and select "New Client"

  • Give the Client a name
  • Select "Regular Web Applications"
  • Press Create



  • Go to the Addons tab 
  • Select SAML 2.0

Application Callback URL

Paste the ACS URL from the Prepare step into Application Callback URL


  • Add audience and recipient (Use the ACS URL from the Prepare step)
  • Press Save, then close the Client setup

Federation Metadata

  • Go to Settings
  • Press "Show Advanced Settings"
  • Press "Endpoints"
  • Copy the SAML Metadata URL

Metadata import

  • In Kantega Single Sign-on, go to the metadata import step
  • Paste the metadata URL from the previous step
  • Press Next


  • Give the Identity Provider a name (This name is visible to end users)
  • The SSO Redirect URL is automatically imported from the metadata
  • Press Next


  • Review the imported signing certificate (This step is purely informational)
  • Press Next.


  • Select whether users already exist, or if you wish to have users automatically created upon login
  • Press Next


  • Review the Summary
  • Press Finish

Testing/configuring the identity provider

After finishing the wizard, you will be sent to the test pages for verification of your setup. Here, you may also perform the last configuration parts. Follow this generic introduction to the test pages and final configuration. AD FS is used as the example here.

  • No labels