-
Bug
-
Resolution: Fixed
-
High
-
5.7.2, 5.13.0.1, 5.14.1
-
4
-
Update:
Steps to Repeat:
On a Bamboo instance using an LDAP directory for authentication...
- Attempt to log into Bamboo using a username that is NOT in the LDAP server yet.
- Add the username to the LDAP server.
- Once the user is synced with Bamboo, it'll be in this funky/bad state where it thinks it's a local user rather than an LDAP user.
- Search for the user in Bamboo admin and click on the "Edit" link.
- OUTCOME: The following error is loaded...
Unable to find the user. The username <em>johnsmith</em> may be incorrect.
Bamboo seems to be hitting some kind of race condition with the identification/storing of users as described above.
Original reporting:
One of our LDAP user is not able to log into Bamboo. The user is found during a user search in Bamboo Admin, BUT when I select the option to Edit the user, it displays an error stating the following...
Unable to find the user. The username <em>user-name</em> may be incorrect.
I found the following article, but it does not appear to be the same issue that we're exhibiting as we already have the LDAP Cache enabled in the ehcache file.
I've tried removing the user from LDAP, making sure he's removed from Bamboo, and then adding him back to our LDAP server but it did NOT resolve the issue.
I also noticed that it's displaying the "Delete" link when it finds the user as if it thinks the user is a local user rather than an LDAP user. I tried deleting the user by clicking on the link and it threw an error. It seems like the user record is corrupt in the user cache. Is there any way to manually clear the user cache?
[BAM-15860] One of our LDAP user is not able to log into Bamboo. Unable to find the user. The username <em>user-name</em> may be incorrect.
Jay Wagner
added a comment - Seen on 6.2.1 build 60208. 
Susant
added a comment - version : 5.14.1 build 51413 Susant
added a comment - Now a days we are getting this error repeatedly, can you please give us a quick fix.
My findings :
1) User who doesn't have access to Bamboo and then they try to login, which shows them an error as no access , once the user gets access and he tries to login the id gets corrupted, it doesn't happens for all but for few.
2) It takes the data from AD as it is connected with LDAP, now for users Bamboo allows to login for the first time as case sensitive and for some users it only allows to login as "capital" and for some as "small", no ides from where Bamboo consider this. once user confirm with captcha then that user becomes case insensitive for both capital and small letters.
Note : I have cross checked my AD users multiple times and many users but it there is no difference as we had a process that the first character of the first name and surname is always capital for all.
Waiting for quick solution here.
Thank you
Regards,
Susant
Susant
added a comment - Now a days we are getting this error repeatedly, can you please give us a quick fix.
My findings :
1) User who doesn't have access to Bamboo and then they try to login, which shows them an error as no access , once the user gets access and he tries to login the id gets corrupted, it doesn't happens for all but for few.
2) It takes the data from AD as it is connected with LDAP, now for users Bamboo allows to login for the first time as case sensitive and for some users it only allows to login as "capital" and for some as "small", no ides from where Bamboo consider this. once user confirm with captcha then that user becomes case insensitive for both capital and small letters.
Note : I have cross checked my AD users multiple times and many users but it there is no difference as we had a process that the first character of the first name and surname is always capital for all.
Waiting for quick solution here.
Thank you
Regards,
Susant
Seeing the same issue on 6.4.0, whats the best solutions for this instead bamboo restart ?