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.
this does not return entryUUID nor ldapId (applies for all bold marked above): ldapsearch -H ldap://localhost:10389 -x -b o=organization -D BINDUSER -w BINDPASS "(uid=*)" "mail" "entryUUID" "ldapId"
but this does (and mixed-case entryUUID and ldapId is received: ldapsearch -H ldap://localhost:10389 -x -b o=organization -D BINDUSER -w BINDPASS "(uid=*)" "mail" "entryuuid" "ldapid"
the point is, that specifying exact case of "entryUUID" is wrong. I have to ask for lowercase "entryuuid" in order to receive attribute "entryUUID" with it's value
this is easily fixable, can I offer a quick PR for this? I believe it's not intended behaviour, as clients shall be able to use upper or lowercase attribute names.
LDAP Attributes are case insensitive, so I believe searching for "ENTRYUUID", "entryuuid" and "entryUUID" shall always return the entryUUID that's defined in the generator function above.
The text was updated successfully, but these errors were encountered:
mgx0
changed the title
LDAPJS Server: when searching, I need to request in lowercase in order to get mixed-case attributes
LDAPJS Server: when searching, I need to request in lowercase attributes in order to get mixed-case attributes
Apr 10, 2024
i have a function that generates LDAP User object from data received from Keycloak and sends it via search response. commented are problematic:
this does not return entryUUID nor ldapId (applies for all bold marked above):
ldapsearch -H ldap://localhost:10389 -x -b o=organization -D BINDUSER -w BINDPASS "(uid=*)" "mail" "entryUUID" "ldapId"
but this does (and mixed-case entryUUID and ldapId is received:
ldapsearch -H ldap://localhost:10389 -x -b o=organization -D BINDUSER -w BINDPASS "(uid=*)" "mail" "entryuuid" "ldapid"
the point is, that specifying exact case of "entryUUID" is wrong. I have to ask for lowercase "entryuuid" in order to receive attribute "entryUUID" with it's value
this is easily fixable, can I offer a quick PR for this? I believe it's not intended behaviour, as clients shall be able to use upper or lowercase attribute names.
LDAP Attributes are case insensitive, so I believe searching for "ENTRYUUID", "entryuuid" and "entryUUID" shall always return the entryUUID that's defined in the generator function above.
The text was updated successfully, but these errors were encountered: