Conversation
added 2 commits
September 10, 2026 21:30
This was referenced Sep 10, 2026
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Discovery, OPTIONS, and LDAP hardening
Testing. Verified against OpenLDAP in a container on PostgreSQL: alice, ALICE and AlIcE all resolve to principals/alice with one account; a cn=-based entry with no uid behaves the same; wrong and empty passwords are still refused; and the case-variant login resolves to a principal that exists and shows its
calendar. 21 new tests, none of which need an LDAP server except the DN ones, which skip without ext-ldap.
Upgrade note. Installs whose stored username differs from the directory's spelling need a one-off rename; the SQL will be in the release note and was applied and verified end to end.