KNOX-2805 - getUserTokens honours different metadata values with the same name#633
Merged
smolnar82 merged 1 commit intoapache:masterfrom Sep 22, 2022
Merged
KNOX-2805 - getUserTokens honours different metadata values with the same name#633smolnar82 merged 1 commit intoapache:masterfrom
smolnar82 merged 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
Cc. @MrtnBalazs |
zeroflag
approved these changes
Sep 22, 2022
stoty
pushed a commit
to stoty/knox
that referenced
this pull request
May 14, 2024
…s with the same name (apache#633) Change-Id: I1ffdfee08fe32c8bada825b9781f7522b9b3bcab
stoty
pushed a commit
to stoty/knox
that referenced
this pull request
May 14, 2024
…a values with the same name (apache#633)" into cdpd-master
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.
What changes were proposed in this pull request?
If the user supplied the same metadata name with different values in Knox's
getUserTokensAPI, the result only contained tokens that matched the first name/value pair. This is now fixed by including all values of each metadata name during the filter logic.How was this patch tested?
I manually tested this feature and added the metadata/expected result matrix in KNOX-2805.
The
curlcommand I used to create the tokens:Here are the
curlcommands and responses I used for verifying my changes: