CT User with umlauts in cn not syncing about ctldap

[milux]

Hey Silas, took a look into this, and Umlauts, Accents etc. are not a problem in general. We have numerous groups with Umlauts, but, funny enough, I think that none of the users from our database with Umlauts in his nickname is a NextCloud user at the same time. 😆
I know from experience that LDAP has some very weird quirks regarding encoding indeed. For instance, user binds have to submit passwords using UTF16LE, at least for AD implementations some years ago, and will silently fail otherwise. Fun.

If you can find out where exactly this gets messed up, we might be able to fix that, but I assume the error in the PHP code of the LDAP plugin. 🙈
Best thing you can do is to ask affected users to change their CT nickname to something without special symbols. An advisable thing anyway...

[milux]

I checked once more. Seems that we used to have users Umlauts in their CN, but with no Umlauts in their NextCloud name. That would be consistent with what I expect.
(So somehow the NC plugin normalized this away, which seems not to happen in your setup, for whatever reason...)