-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 5.9.3, 5.12.3.1
-
Component/s: Permissions, User Management, Crowd & LDAP integration
-
Severity 3 - Minor
-
1
Summary
When adding a group or user in global or plan permissions, Bamboo does not check for case sensitivity of the added name. However, names are case sensitive when used to verify if the user or group has permission.
Environment
When using LDAP user repositories or Crowd
Steps to Reproduce
- Create a group/user named MixedCase in Crowd
- Add group/user mixedcase in Bamboo Global or Plan Permission Access
Expected Results
Bamboo should throw a Group not found error as the cases does not match
Actual Results
The group/user is added successfully to the global/user permission. However, users/groups will still have no access as usernames group names are supposed to be case sensitive
Workaround
- When adding group/user permission, ensure that they are in the correct case
- Alternatively, configure groups to use lower case in Bamboo and enforce lower case in Crowd
https://confluence.atlassian.com/display/CROWD/Enforcing+Lower-Case+Usernames+and+Groups+for+an+Application
- relates to
-
BDEV-13854 Loading...
- was cloned as
-
BDEV-10164 Loading...