Repository navigation
Conversation
Encode the UID as LDAP filter data and update the case expectation with focused regression coverage.\n\nCo-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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.
Benchmark case 44 interpolated the request UID directly into an LDAP search filter, allowing filter metacharacters to alter the query. This encodes the UID as LDAP filter data, adds regression tests for ordinary and metacharacter input, and updates only case 44's expected result.
Validation:
mvn -q -Dspotless.apply.skip=true -Dtest=LDAPManagerTest testpasses. The configured Spotless formatter could not run because google-java-format 1.17.0 is incompatible with the installed JDK 27.