Skip to end of metadata
Go to start of metadata

Bilderesultat for ws02 logo


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



Add a new Application

  • Log into WS02 
  • Select Add Application
  • Choose Custom Application
  • Enter an Application Name
  • Select Add

 

Adding an identity provider

In Kantega Single Sign-on add an identity Provider of the type "Any SAML 2.0 Identity Provider".



Prepare

Copy the ACS URL. You will use this in the next step.

Configure the application

  • Fill in the URL from the previous step into the following fields:
    • Issuer
    • Assertion Consumer URL´s (Press Add)
    • Access URL
  • Save


Download IDP Metadata

  • Download the IDP metadata. You will use the metadata file in the next step.

Metadata Import

  • In Kantega Single Sign-on, go to the metadata import step.
  • Browse and select the downloaded metadata file from the previous step.
  • Press Next.


Location

  • 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.

Signature

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

Users

  • Select whether users already exist or if you wish to have users automatically created upon login.
  • Optionally assign a default group for new users.

Summary

  • 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