fix: Pass resolved token to OPA policy checks#927
Open
MohidSheraz wants to merge 1 commit into
Open
Conversation
Signed-off-by: Mohid Sheraz <msheraz@andrew.cmu.edu>
eb021ff to
ecbfe35
Compare
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.
Closes #715
This updates token show and revoke policy checks to pass the resolved token response object to OPA instead of the raw FernetToken payload.
The subject token is already validated into a ValidatedSecurityContext. This change builds the resolved token object from that context and uses it as the policy target for:
The revoke backend still receives the raw token payload because it needs the internal token data for revocation.
Note: Used CodeX for assistance.