Redmine

+1
I ran into the same problem with 1.3.0 and used the same "hack" to fix it (I manually edited user.rb).
Why hasn't this patch been incorporated?
Why is that validation necessary, anyways?

Just stumbled upon the same issue with danish characters. The name of this thread should maybe be changed to "national characters in login string" or something. Anyway the difference for me was that these national characters are not ASCII, and apparently the app/models/user.rb file in its unmodified form is ASCII encoded. So I needed to add the following code on the very top of the file:

# -*- coding: utf-8 -*-

Well we encountered the same Problem. It would be great to have this enabled in the next release.
I currently disabled just the Loginname validation as we are using LDAP for our user management. But this way we just need to change some core code on every release to get this thing working.

I just want to add myself as one more victim of this shortcoming. It's 2013 and we should be able to use proper usernames by now. Please consider to extend the allowable characters.

I also just came across this issue where I was authenticating against LDAP.
This user had a german 'umlaut' in his user name and redmine always was rejecting a login with 'invalid user name'

The fix from Max Meier works for me in Redmine 2.6.3
So thanks to Max!

It is not only login causing issues when containg umlauts.
I also get an Internal error

An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.
If you are the Redmine administrator, check your log files for details about the error.

during account creation on first time login by LDAP.
This is also caused by umlauts in first name/Last name

account creation through normal register procedure is working, when first name/Last name contain umlauts.

int redmine wrote:

It is not only login causing issues when containg umlauts.
I also get an Internal error

This is because of #21453.

+1
I ran into the same problem with Redmine version 3.2.0 and successfully used the patch above to overcome the limitation I encountered.
I would appreciate if this issue could be addressed in a future version of Redmine.

More than 6 years later, I again ran into the same problem when updating my Redmine instance to version 4.2.4. Again, I successfully used the patch above to overcome the limitation I encountered.
I really would like to see this issue addressed in future Redmine versions.

Pleas note, that I'm not the only one, this note

https://www.redmine.org/issues/6166 is basically the same problem with german characters, but no one seems to be interested.

+1