Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Unable to login to Jira after enabling Crowd SSO

Armaan Bajwa June 21, 2019

I have a Jira docker image set up to communicate with Crowd. The login with Crowd users works when SSO is disabled, but I cannot login to Jira with any user at all once I enable SSO using Crowd.

Following this guide, I made the following changes to my Jira Docker image:

seraph-config.xml was changed to:

<!-- CROWD:START - If enabling Crowd SSO integration uncomment the following SSOSeraphAuthenticator and comment out the JiraSeraphAuthenticator below -->
<authenticator class=""/>
<!-- CROWD:END -->

<!-- CROWD:START - The authenticator below here will need to be commented out for Crowd SSO integration
<authenticator class=""/>


I also added a file that contained the following information: jira-8
application.password test
application.login.url http://crowd-url/crowd/console/

crowd.server.url http://crowd-url/crowd/services/
crowd.base.url http://crowd-url/crowd/

session.isauthenticated session.isauthenticated
session.tokenkey session.tokenkey
session.validationinterval 1
session.lastvalidation session.lastvalidation
cookie.tokenkey crowd.token_keyroot@<key>:/opt/atlassian/crowd/client/conf#


After I make these changes and restart the Docker container, I'm unable to log in to Jira with any credentials (I tried both Crowd credentials, and Jira local credentials)

1 answer

0 votes
Bruno Vincent
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 30, 2019

Hi @Armaan Bajwa 

You cannot login with a Jira internal directory user once Crowd SSO is enabled, it is a known limit as per Atlassian's documentation (see section 2.2).

Regarding Crowd users, this might have something to do with IP addresses consistency or your SSO domain name. I suggest that you set the following property in atlassian-jira/WEB-INF/classes/ and restart Jira. You will then get more information in atlassian-jira.log that should hopefully help you to understand what is going on here. = DEBUG

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events