Add mTLS client certificate information to APIGatwayV2Request #45
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
tomerd
reviewed
Feb 5, 2024
|
@swift-server-bot test this please |
|
@tomerd * polite cough * |
tomerd
approved these changes
Feb 13, 2024
|
thanks @sliemeobn and sorry about the delay |
|
no worries, thanks for merging! |
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.
Add mTLS client certificate information to
APIGatwayV2RequestMotivation:
When configuring mTLS in API Gatway (HTTP v2), the event payload contains information about the client certificate. This information is currently not present in the
APIGatwayV2Requeststructure.Modifications:
Added optional fields for
authentication.clientCertonAPIGatewayV2Requestaccording to the AWS "spec".Result:
mTLS client certification information is decoded and passed to the lambda handler.