Michael Aldridge d74308280b internal/ldap: Reply with the result type a request expects ... An LDAP client only accepts the result that pairs with the request it sent, and silently ignores anything else. Unrouted operations were answered with a generic result, which encodes with the wrong tag, so a search with an unexpected base DN (for example the empty base that ldapsearch uses when -b is omitted) left the client waiting forever instead of reporting an error. Every failure path now terminates the request with the matching result type, panics included, so a single wrapper covers all operations rather than one responder per operation. NetAuth calls carry a 30s deadline because the gRPC client dials lazily and applies none of its own, and refused operations and failed authentication are logged, which is what an operator needs when a client appears to hang. 💘 Generated with Crush Assisted-by: Crush:qwen38_flash_next_mtp		2026-11-02 19:59:04 -06:00
..
buildinfo	internal/ldap: Handle bind	2020-08-22 20:49:54 -07:00
ldap	internal/ldap: Reply with the result type a request expects	2026-11-02 19:59:04 -06:00