Crowd SAML app gives the ability to enable SAML Single Sign-On for JIRA, Confluence, Bitbucket, Bamboo, Fisheye, and other connected applications from any SAML Identity Providers. Here we will go through a guide to configure SSO between Crowd and Identity Provider. By the end of this guide, your IdP users should be able to login and register to Crowd Software.
To configure your Identity Provider integration with Crowd SAML SSO, you need the following items:
Follow the steps below to configure Jboss Keycloak as an Identity Provider.You can use 2 ways to configure the JBoss Keycloak as IDP.
Method 2: Manual Configuration
|Client ID||The SP-EntityID / Issuer from the step 1 of the plugin under Configure IDP tab.|
|Name||Provide a name for this client|
|Description||Provide a description|
|Optimize Redirect signing key lookup||OFF|
|Client Signature Required||OFF|
|Force Name ID Format||ON|
|Name ID Format|
|Root URL||Leave empty or Base URL of Service Provider|
|Valid Redirect URIs||The ACS (Assertion Consumer Service) URL from the step 1 of the plugin under configure IDP tab.|
|Assertion Consumer Service POST Binding URL||The ACS (Assertion Consumer Service) URL from the step 1 of the plugin under Configure IDP tab.|
|Logout Service Redirect Binding URL||The Single Logout URL from the step 1 of the plugin under Configure IDP tab.|
Download IDP Metadata
The Crowd SSO connector expands the SAML SSO functionality from Crowd to its connected Atlassian applications where it allows users to login to their applications such as Jira, Confluence, Bitbucket, Bamboo, Fisheye while maintaining the users in Crowd.
Note: Click on the icons to view the SSO Connector guide for the application.