Bamboo user from Crowd has no groups when "Enable Aliasing" is on in Crowd 2.10+

Summary

When "Enable Aliasing" is allowed for the application Bamboo in Crowd 2.10+ and a user has an alias, once synced to Bamboo – the user has no groups.

The call to http://crowdurl/crowd/rest/usermanagement/1/group/membership is not returning the aliased user name in Crowd 2.10+ when authenticated with the application credentials. This is causing problems mapping the groups back to the aliased users.

Other Bamboo calls such as http://crowd/crowd/rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=-1&expand=user return the aliased username.

Environment

• Crowd 2.10+ (cannot reproduce on 2.9)
• Bamboo 5.14.3.1 (also affects other versions)

Steps to Reproduce

1. Integrate Bamboo with Crowd 2.10+ for user management
2. Crowd > Applications > Bamboo > Options > Enable Aliasing
3. Add a bamboo-user group within a directory associated to the Bamboo application
4. Add a second group within a directory associated to the Bamboo application e.g. "test"
5. Add a new user to the bamboo-user & test group.
6. Under User > Applications set an alias for the application Bamboo
7. Bamboo Administration > Overview > User repository > Syncronize now

Expected Results

Under Bamboo Administration > Overview > Users the user with an alias should have two groups.

Actual Results

Under Bamboo Administration > Overview > Users the user with an alias has no groups.
This severely impacts Bamboo permission schemes based upon groups.

Workaround(s)

1. Disable aliasing on the Crowd side and resync the user directory in Bamboo.
   or
2. Add the user directly to permissions for build / deployment plans, as opposed to group based permissions.