Bamboo: Is it possible to have both a internal user and Crowd LDAP external?


I would like a designated build user in Bamboo with a password that never expires.

We currently use Crowd to manage our users via our corporate LDAP server.  

We are starting to implement various types of automation through the API and I'm currently using my corporate username/password which I'm forced to change every 60 days.  I encode my password but every time it changes I have to go through all the plans and scripts to make sure I update them with the new password. 

Bamboo only allows internal OR external.  I've tried to create a non-ldap user in Crowd and assign it to my Bamboo application, add that user to the same Bamboo group as myself, synchronize but I'm not able to log in to Bamboo as that user (the user shows up in the user list).  Do I need to get IT to create a LDAP user for this?

What would my options be?

Thank you for your time.

2 answers

Hi Lloyd,

Your setup should work. As you see your user in the Bamboo try setting him permissions directly in 

Bamboo administration=>Security=>Global permission (to be sure that you didn't mess with groups).

Hope this helps.

Hello Sergey, 

I appreciate the response. 

I added the user I had created in Crowd (only - doesn't exist in LDAP like my user info) to the User section with full Admin rights to the Global Permission section but was still not able to either log into Bamboo as that user or successfully invoke a API as that user - it returns "Basic Authentication Failure - Reason : AUTHENTICATION_DENIED".

When I switch out that user info with mine its successful.

I did just notice that under Security=>Security Settings that "Enable Signup?" is NOT checked.  I actually only have "Read-only external user management?" checked.   

I could try turning that on and seeing if that is restricting something. 

Thank you again for your time. 


Check your application configuration in Crowd. Did you allow authentication from the internal directory?


No, only the LDAP directory is specified. So, configuring a Crowd internal directory that can contain internal valid users who do not need to be in LDAP? 

I appreciate your time. 

WooHoo!! It worked.  I created an internal directory in Crowd, added a build user to that internal directory, added that directory to my Bamboo application, sync'd with Bamboo and then added that new user to the Global Permissions as admin and it worked!! It's now a valid internal user .. with a password that never expires. 

Thank you very much Sergey for your time and assistance!!

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,096 views 0 5
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot