Description
If you call the /session REST service to create a new session token the username that gets returned in the response has the same case as the username that was passed through, e.g.
Username as appears in the directory:
test@example.com
Call the /session service:
<authentication-context> <username>tEst@EXAMPLE.com</username> <password>password</password> </authentication-context>
Response:
<session expand="user"> <token>0fX2yGuAWNdhuaMawedehQ00</token> <user name="tEst@EXAMPLE.com"> <link rel="self" href="http://idm-access-staging.private.atlassian.com:8081/crowd/rest/usermanagement/1/user?username=tEst@EXAMPLE.com" /> </user> <link rel="self" href="http://idm-access-staging.private.atlassian.com:8081/crowd/rest/usermanagement/1/session/0fX2yGuAWNdhuaMawedehQ00" /> </session>
The response should have returned the username in the original case (test@example.com) like the other Crowd REST services. It should also follow the "Lower Case Output" option set on the application calling the REST service.
Attachments
Issue Links
- causes
-
CWD-3219 SSO tokens should be stored with unaliased usernames
-
- Closed
-