You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 14, 2024. It is now read-only.
When searching a value that contains umlauts, the filter string is encoded in a way our AD does not seem to understand. It does not return any search results. When searching values without umlauts everything works fine.
I didn't have this problem with ldapjs v2. Any idea how to fix this?
EDIT: I found escapeFilterValue und RFC4515, so this seems to work as expected. I'm still not sure if our active directory is to blame, I'm part of a larger corporation and I haven't heard of similar problems in other apps.
The text was updated successfully, but these errors were encountered:
When searching a value that contains umlauts, the filter string is encoded in a way our AD does not seem to understand. It does not return any search results. When searching values without umlauts everything works fine.
Minimal reproduction:
I didn't have this problem with ldapjs v2. Any idea how to fix this?
EDIT: I found escapeFilterValue und RFC4515, so this seems to work as expected. I'm still not sure if our active directory is to blame, I'm part of a larger corporation and I haven't heard of similar problems in other apps.
The text was updated successfully, but these errors were encountered: