search

RocketChat / Rocket.Chat

The communications platform that puts data protection first.
https://rocket.chat/
Other
40.63k stars 10.63k forks source link

LDAP - problem with umlauts #3451

Open hhenkel opened 8 years ago

hhenkel commented 8 years ago

Your Rocket.Chat version: 0.32

When using rocket.chat with an active directory as ldap backend we see that umlauts (äöü) are not shown propably. It seems that "ä" is mapped to "a" - is this purpose? IMHO it would be better to show the actual letter or to convert it to "ae".

d-sko commented 7 years ago

Same here with Rocket.Chat connected to a Active Directory on Windows Server 2012 R2

geekgonecrazy commented 4 years ago

Somewhat related: https://github.com/RocketChat/Rocket.Chat/issues/7586

nemhods commented 4 years ago

So with the change from meteor-slugify to limax and therefore speakingurl, what @hhenkel asked for is now the case. However, this breaks LDAP Syncing.

This is an issue in at least 3.7.0. Consider a username Max.Müstermann. I have the username attribute set to sAMAccountName. For sAMAccountName "max.müstermann", Rocketchat accepts Logins with

However, the account is created with the RocketChat name "max.muestermann".

Now, the issue is that an ldapfilter with (sAMAccountName=max.muestermann) returns no results. Therefore, Group/Role sync does not work, since the user (sAMAccountName=max.muestermann) does not exist in the LDAP context.

It would be great to have a replacement option for %{objectGUID} in the LDAP Group search filter.