'Lower Case Output' option in Crowd can cause InvalidUserException in JIRA

[熊井 亮輔]

Situation

• Crowd
  • Crowd version is 2.5.3
  • User with Upper case username K0000 has been added to Crowd.
  • User with Lower case username k0001 has been added to Crowd.
  • 「Applications」(JIRA) - 「Options」 - 「Lower Case Output」 is turned on.
  • 「Applications」(JIRA) - 「Permissions」 - 「Modyfy User」 is turned on.
• JIRA
  • JIRA version is 5.2.5.
  • Integrating JIRA with Crowd.
  • 「Crowd Permissions」 - 「Read/Write」 is turned on.
  • 「User Directories」 - 「Synchronise」
  • User with Lower case username k0000 has been added to JIRA.
  • User with Lower case username k0001 has been added to JIRA.
  • k0001 edited successfully the e-mail address.
    
  • k0000 failed to edit the e-mail address, and InvalidUserExcepton is occured.
    see an attachment Error.png, atlassia-jira.log.

I think Crowd can`t handle Upper case username when Lower Case Output is turned on.
How do should I solve this problem.

Could you give us any advice?

Error.png

[joe · Accepted solution]

I believe you're running into an issue reported as CWD-3307 ("Usernames in updates posted to /user should be checked case-insensitively"). This is fixed in Crowd 2.6.3.

[熊井 亮輔]

Thanks Jeseph.

I confirmed that the problem can be solved by upgrade to Crowd 2.6.3.

[熊井 亮輔]

Thanks John.
Thanks Jeseph.

I try to run Crowd 2.6.3. and I will report the results at a later date.

[JohnA]

Hi Ryosuke,

This is in fact expected behaviour because Crowd will convert the uppercase username to lower case when the "enforce lower case" option is set, meaning Crowd will convert any upper-case and mixed-case information, (usernames etc), to lower case before passing the information to the application.

So enabling this option should only be done when the application is expecting lowercase usernames because it will cause incoherence if it is enabled and you pass content containing uppercase characters as described in this document: https://confluence.atlassian.com/display/CROWD/Enforcing+Lower-Case+Usernames+and+Groups+for+an+Application

All the best,
John