Trouble logging into Bamboo

[Todd Ellner]

Our Bamboo installation is (mostly) working fine. I recently added a user - username "tools", with a working email. Whenever I try and log in I get the "You have  entered an invalid username or password" error. The logs show:

2015-04-08 09:26:53,559 INFO [http-bio-8085-exec-3] [DefaultAuthenticator] login : 'tools' could not be authenticated with the given password
2015-04-08 09:26:53,559 WARN [http-bio-8085-exec-3] [DefaultAuthenticator] login : 'tools' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.

I've tried using the Forgotten Password feature.

2015-04-08 09:54:44,431 INFO [http-bio-8085-exec-61] [DefaultAuthenticator] login : 'tools' could not be authenticated with the given password
2015-04-08 09:54:44,431 WARN [http-bio-8085-exec-61] [DefaultAuthenticator] login : 'tools' tried to login but they do not have USE permission or weren't found. Deleting remember me cookie.
2015-04-08 09:54:44,445 INFO [http-bio-8085-exec-61] [AccessLogFilter] 10.10.254.224 POST http://bamboo1.via.act-on.net:8085/userlogin.action 97096kb
2015-04-08 09:54:44,762 INFO [http-bio-8085-exec-61] [AccessLogFilter] 10.10.254.224 GET http://bamboo1.via.act-on.net:8085/rest/pref/latest/user/?expand=preferences.preference 91251kb

2015-04-08 09:54:49,518 INFO [http-bio-8085-exec-61] [AccessLogFilter] 10.10.254.224 GET http://bamboo1.via.act-on.net:8085/forgotPassword!default.action 87865kb
2015-04-08 09:54:49,546 WARN [http-bio-8085-exec-61] [ServletUrlRenderer] No configuration found for the specified action: 'forgotPassword.action' in namespace: '/'. Form action defaulting to 'action' attribute's literal value.
2015-04-08 09:54:49,554 WARN [http-bio-8085-exec-61] [ServletUrlRenderer] No configuration found for the specified action: 'forgotPassword.action' in namespace: '/'. Form action defaulting to 'action' attribute's literal value.
2015-04-08 09:54:49,853 INFO [http-bio-8085-exec-61] [AccessLogFilter] 10.10.254.224 GET http://bamboo1.via.act-on.net:8085/rest/pref/latest/user/?expand=preferences.preference 82638kb

It sends a link to the registered email. I follow the link and change the password. I go through the change password process and the server says to log in. It still doesn't work. I've tried removing and re-adding the user, making sure it is in specified CROWD-defined groups and changing the password through administration screens. Nothing seems to work

The username shows up when I look at users.

The only hint I can find is the "they do not have USE permission", but a search of the documentation on how to change that has come up dry so far.

Any help would be appreciated

[rsperafico · Accepted solution]

Hello Todd,

Thank you for your question.

Based on the description provided, I am not able to identify if you have added the user "tools" in Bamboo's Internal Directory or Crowd. However, if the issue is permissions, could you please make sure the user has permissions to log in under "Bamboo administration >> Security >> Global permissions".

Please, refer to Granting global permissions to users or groups documentation for further information.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

—

Kind regards,
Rafael P. Sperafico
Atlassian Support

[Mezonox]

I'm sure this has since been resolved with newer versions. We're currently running Crowd v2.8.0 and Bamboo v5.7.2. I tried all of the suggested fixes and none of them worked. I was finally able to resolve the problem by clicking on everything I could find.

Once you've synchronised the user repositories and your group is visible in Bamboo, you have one more step to go through. Hop on over to Crowd, select "Applications" from the top navigation bar, then select Bamboo from the Applications list. Select the "Groups" tab and add your group to this list. This fixed it for me.

You can probably also resolve this by going to the "Directories" tab and changing the desired directory's "Allow all to authenticate" value to True. This is probably the more general way of doing it, but I'm keeping our Bamboo access restricted on a group basis.

[Todd Ellner]

I had already considered that and edited the global permissions giving tools access and create plan permissions. I even tried giving it restricted admin rights, so that's probably not the problem. I've tried adding the user by hand to the internal database and removing the user to see if it would pick up on CROWD which we use for SSO.