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
root@c80b3172-b6b5-479b-9c5b-aa9967a2b632:/opt/goklp/etc# sudo -u goklp /opt/goklp/etc/goklp nate2024/06/19 18:31:29 Error in query while looking for keys for nate: Too many results found.2024/06/19 18:31:29 Successfully found 0 keys for nate
This is related to glauth/glauth#181 and the somewhat unusual duplication of groups into the users OU and DN construction choices.
This is easily worked around with the following additional filter:
Ohhh damn.
I am always amazed at, with all the complexities that exist in LDAP and its extensions, the biggest headaches are due to GLAuth attempting to simplify users and groups while remaining correct.
I appreciate GLAuth's goal of simplification, it's why I'm planning to replace my small slapd setup with it! Unfortunately there are so many different client configurations and expectations.
In my case I have a user
nate
with primaryGroupnate
, this results in two results for the(uid=$user)
filtered query in goklp:And thus goklp fails due to multiple results:
This is related to glauth/glauth#181 and the somewhat unusual duplication of groups into the users OU and DN construction choices.
This is easily worked around with the following additional filter:
But I do wonder if it would be a good idea to prevent groups from appearing under the users OU and sort out the DN issues in general.
The text was updated successfully, but these errors were encountered: