Details
-
Bug
-
Resolution: Fixed
-
High
-
5.7.2, 5.13.0.1, 5.14.1
-
4
-
Description
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?