feat(xds): Implement response handling for external authorization #12495
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.
This PR sits on top of #12494, so only the last commit + any fixups need to be reviewed.
This commit introduces the
CheckResponseHandlerandAuthzResponseclasses, which are responsible for processing responses from the external authorization service.The
CheckResponseHandlerparses theCheckResponseprotobuf, determines whether the request should be allowed or denied, and applies any header mutations specified in the response. It handles bothOkHttpResponseandDeniedHttpResponsemessages.The
AuthzResponseclass is a value object that represents the outcome of the authorization check, encapsulating the decision (allow or deny), the status to be returned to the client (for deny decisions), and any header mutations.The relevant section is: https://github.com/grpc/proposal/pull/481/files#diff-6bb76a24aa142cc33db9218509688f01b30c8885d2fd8849f164244e68cd54eaR252-R282
This commit also includes unit tests for the new components.