Marcus,
I didn't check yet (I will later) for what concerns Zentyal implementation but as far as LDAP is concerned and as long as what you call "user name" is based on [
UID] ldap attribute:
- this attribute is defined as CIS, standing for Case Insensitive String
- this attribute may contain blank in the middle
As a result, and again from LDAP standpoint only, "My Login", "my login" "MY LOGIN" are all (w/o quotes) valid and equivalent logins.
Long time ago
blank in the middle was not supported by Unix systems like HP-UX and Solaris and this prevented NIS-LDAP gateway to work properly reason why LDAP administrators where pushing to avoid such kind of UID but there is no LDAP limitation here (at least as long as standard LDAP server with standard schema is used.
This is slightly different with AD
Reason why I was stating that "HTTP error 500" is, from my standpoint, a bug is that "user corner" application handles authentication process. Even is something goes wrong LDAP side, this should not be reported as "Err 500".
This being said, problem is maybe not with LDAP but then even if workaround is not to use blank in the middle and upper case, this is not the right technical solution, at least to me