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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to log into Bamboo Dashboard with LDAP users

I have configured LDAP and see the users I expect to see from that directory in user management; however, when I try to log in as one of those users it responds that the password is incorrect.

I see the following errors in atlassian-bamboo.log

  • could not be authenticated with the given password
  • tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

I followed the directions at

I configured caching.

I have provided Access, Create, Create repository and Admin permissions under Global permissions.

This is a new install of Bamboo 6.4.0 running on Windows Server 2012.

I'm using the same LDAP for Bitbucket and that works without issue.

1 answer

0 votes
Jeyanthan I Atlassian Team Apr 01, 2018

As you say that the users are able to login to other applications and the user is listed in Bamboo and is granted appropriate permission, it is most likely that the user is not added to the appropriate group on LDAP that has rights to authenticate to the Bamboo server.

If you still have issues and if this problem is caused by the cache, a Bamboo restart should fix it.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events