Membership endpoint is not returning the aliased user name

Summary

When "Enable Aliasing" is allowed for the application Bamboo or JIRA in Crowd 2.10+ and a user has an alias, once synced to Bamboo or JIRA – 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 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) or JIRA 7.0.2

Steps to Reproduce

1. Integrate Bamboo or JIRA with Crowd 2.10+ for user management
2. Crowd > Applications > Application Name (Bamboo or Crowd) > Options > Enable Aliasing
3. Add a group within a directory associated with the application
4. Add a second group within a directory associated with the application e.g. "test"
5. Add a new user to each of the groups created above
6. Under User > Applications set an alias for the application Bamboo
7. Synchronize the Crowd connected directory in your downstream application

Expected Results

The user with an alias should have two groups.

Actual Results

The user with an alias has no groups.
This severely impacts downstream application 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 as opposed to group based permissions.