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

Cannot Login With Jira or Confluence But Can With Bitbucket

europoint March 15, 2020

I am running Bitbucket, Confluence and Jira Server as Docker containers, all connecting to a Crowd server also as a Docker container.

I recently replaced the Crowd Docker Container, changing it from alvistack/Crowd to Atlassian/Crowd, ran a clean install and then imported my last Crowd backup.

I can log in to Crowd with my user, and can also do the same with Bitbucket.

However, I can't log in via Jira or Confluence. The application configuration in Crowd, and in the for both Jira and Confluence are unchanged and match. The URL to access Crowd is the same (

The Crowd API endpoint is at

I suspect that Jira and Confluence are trying to call the API at instead of /crowd/rest, but I have no way of knowing. Where would I change this to check that this is correct?

I have checked authentication of the user for each application within Crowd, and the authentication is successful. The issue appears to be with communicating with Crowd itself.

However, that atlassian-confluence.log displays the following. The jira-security.log is less detailed but also states: tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

2020-03-15 16:12:50,650 WARN [http-nio-8090-exec-13] [atlassian.seraph.auth.DefaultAuthenticator] login login : '' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.
 -- referer: | url: /dologin.action | traceId: 1996c261e88dda12
2020-03-15 16:12:50,845 INFO [http-nio-8090-exec-13] [] recordLoginFailure
Failed login attempt for user '':
  Request URL:
  User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:74.0) Gecko/20100101 Firefox/74.0
  Remote Address:



1 answer

1 accepted

0 votes
Answer accepted
europoint March 16, 2020

I was correct in realising that the file needed updating, to insert the crowd directory in the file structure:                      {}
application.password                 {application.password}


previously the file was configured as:                        {}
application.password                    {application.password}

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events