fix(ldap): parentheses not mandatory for MUST and MAY#940
Merged
marle3003 merged 1 commit intomarle3003:mainfrom Apr 21, 2026
Merged
fix(ldap): parentheses not mandatory for MUST and MAY#940marle3003 merged 1 commit intomarle3003:mainfrom
marle3003 merged 1 commit intomarle3003:mainfrom
Conversation
Owner
|
Thank you for your continued contributions to resolving LDAP issues. This ongoing support is incredibly helpful. I truly appreciate it! |
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
2 participants
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.
Parentheses are not mandatory when MUST or MAY are only followed by one oid for objectClasses (RFC 4512 4.1.1)
The MUST Part of the altered Regex can now, after the matching, include the keyword MAY and the oids listed behind that. This is cleaned up and splitted in the added if clause.