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

Bilderesultat for salesforce logo

Setup guide for adding Salesforce 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.

Adding an identity provider

In Kantega Single Sign-on add an identity Provider of the type "Salesforce".


  • Copy the ACS URL and Entity ID values and save them for later.

  • Click Next.

Adding an app in Salesforce

Our guide uses the Salesforce Classic user interface.

Login to Salesforce as admin. In the upper right corner select your account and Switch to Salesforce Classic

Then select Setup.

New Connected App

  • Locate Build in the left menu
  • Select Create, then Apps

Create new Connected App

  • Under Connected apps, press New

Basic Information

  • Fill in the required fields

Web App Settings

  • Select Enable SAML
  • From the Prepare step:
    • Fill Entity ID
    • Fill ACS URL
  • Press Save, then Manage

Give permssions

  • Select Manage Profiles

  • Give users permission to log into the App (In this test we use the profile - Free User
  • Press Save

Metadata export

  • Under SAML Login Information press "Download the metadata"
  • Go back to Kantega Single Sign-on

Metadata import

  • Import the downloaded metadata 
  • Press Next


  • Give the IDP a proper name
  • The SSO redirect URL is imported from the metadata
  • Press Next


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


  • Select whether users already exist or if you wish to have users automatically created upon login.
    • To automatically create users, Salesforce needs to send a Name and the email in addition to the user name attribute (Not covered in this guide)

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