Bamboo failing to bind to Active Directory (LDAP) Server Edited

I'm attempting to configure Bamboo to talk to our active directory server following the instructions at - I've ended up with an xml file that looks quite similar to

Whenever I try and load this config, though, it looks as though Bamboo is not attempting to authenticate and bind before it executes queries against AD. Whenever I switch i get a stack track with the "must bind before executing query" error. 

I've validated several options as below to try and narrow down the problem:

Incorrect hostname: Failed to lookup host error (Good)

Incorrect port: Failed to connect error (Good)

Incorrect username: Failed to bind error (so it is even trying? - I'd expect an "invalid credential" error)

Incorrect password: Failed to bind error (so it is even trying? - I'd expect an "invalid credential" error)

Has anyone seen this before and know why its happening? I'm hoping its just a missing setting. Please be aware that this is a customer project and as such I'm unlikely to be able to post logs directly. Thanks in advance for any help!

1 answer

Verify you have the correct username/password to connect to the AD server. I believe the "bind" refers to authenticating to AD and establishing a connection.

I had the issue with my crowd server and I had to fully qualify the username something like this...


If you don't know the fully qualified name, download AD Explorer (Free tool from microsoft) connect to your AD server and search for your user and it should tell you.

Thanks for the reply!

I've tried with both the fully qualified name and the abbreviated "user@domain" style names and neither works - both of these can query AD succesfully through ldapsearch on a Linux command line.

When I deliberately get the password or username wrong through a direct LDAP lookup, it comes up with an "Invalid Credentials (49)" error as opposed to the error Bamboo is throwing:

"LDAP: error code 1 - 000004DC: LdapErr: DSID-0C090752, comment: In order to perform this operation a succesful bind must be completed on the connection"

Which is seems to throw whether the user and password is right or wrong.

Thanks again - I've double checked by pulling the user CN from AD directly and pasting into the xml file - and the password has been reset to something simple and double checked. Unfortunately (as it would be the simplest answer!) both look completely correct, but still getting the bind error.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

387 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you