ldap search filters - allow literal expression #163
Merged
Conversation
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
Older implementation assumed all ldap filters end with "={0}"
This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like
((&(member={0})(objectclass=posixgroup)(!(cn=admin)))
above is example IPA group search filter for ECS 1.5.x
Signed-off-by: Chuck Levesque <[email protected]>
wmudge
added
the
enhancement
github-actions
bot
added
validated
Older implementation assumed all ldap filters end with "={0}"
This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like
((&(member={0})(objectclass=posixgroup)(!(cn=admin)))
above is example IPA group search filter for ECS 1.5.x
Signed-off-by: Chuck Levesque <[email protected]>
github-actions
bot
added
validated
|
Had to make a simple fix, I relocated j2, file into templates/ where it belongs |
Older implementation assumed all ldap filters end with "={0}"
This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like
((&(member={0})(objectclass=posixgroup)(!(cn=admin)))
above is example IPA group search filter for ECS 1.5.x
Signed-off-by: Chuck Levesque <[email protected]>
github-actions
bot
removed
the
validated
|
Fixed jinja syntax error |
Older implementation assumed all ldap filters end with "={0}"
This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like
((&(member={0})(objectclass=posixgroup)(!(cn=admin)))
above is example IPA group search filter for ECS 1.5.x
Signed-off-by: Chuck Levesque <[email protected]>
github-actions
bot
removed
the
validated
|
Fixed a minor typo |
wmudge
approved these changes
Dec 6, 2023
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.
Older implementation assumed all ldap filters end with "={0}" This newer implementation allows the user to craft any legal filter expression, including complex compound expressions, like ((&(member={0})(objectclass=posixgroup)(!(cn=admins))) above is example IPA group search filter for ECS 1.5.x