Username containing a space at the end will make the user from Crowd server unable to login

Steps to reproduce

1. Create a username 'admin ' (with a space at the end) in Crowd server (2.1.1 and 2.2.7)
2. Integrate JIRA 4.4 with Crowd server and synchronize the directory
3. Login with the username 'admin' (without a space) will have the following error:

   2011-08-08 11:03:20,411 http-8440-1 ERROR      [500ErrorPage.jsp] Exception caught in 500 page user should not be null!
   com.atlassian.jira.util.dbc.Assertions$NullArgumentException: user should not be null!
   	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:26)
   	at com.atlassian.jira.security.login.LoginManagerImpl.authorise(LoginManagerImpl.java:135)
   	at com.atlassian.jira.security.JiraRoleMapper.canLogin(JiraRoleMapper.java:46)
   	at com.atlassian.seraph.auth.DefaultAuthenticator.isAuthorised(DefaultAuthenticator.java:229)
   	at com.atlassian.seraph.auth.DefaultAuthenticator.authoriseUserAndEstablishSession(DefaultAuthenticator.java:197)
   	at com.atlassian.seraph.auth.DefaultAuthenticator.login(DefaultAuthenticator.java:102)
   	at com.atlassian.seraph.filter.PasswordBasedLoginFilter.runAuthentication(PasswordBasedLoginFilter.java:127)
   

4. User must login with username 'admin ' (with a space at the end)
5. The same thing happen to JIRA 4.3 without any error in the log

The screenshot is a test login with username 'test' (without space) and the Crowd username is 'test ' (with a space)

When login with other user, we can see that a lot of JIRA function related to this username 'admin ' (with a space) is broken such as the Activity Stream

Workaround
Modify Crowd database for the username with XML backup

1. Export the Crowd database to XML backup
2. Check and edit the username in the XML backup (it seems that the space is not exported to the XML)
3. Re-import the XML to Crowd server and synchronize Atlassian application again with Crowd