API Gateway proxy request should have a client cert field under the requestContext.identity field. This can be seen in the docs https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html. Had to use a pointer and omitempty otherwise unmarshaling and then marshaling results in a client cert field being populated with zero values. Updated test data to include sample data from the docs and also updated test case to verify those values are present after unmarshaling.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: N/A
Description of changes:
API Gateway proxy request should have a client cert field under the requestContext.identity field. This can be seen in the docs https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html. Had to use a pointer and omitempty otherwise unmarshaling and then marshaling results in a client cert field being populated with zero values. Updated test data to include sample data from the docs and also updated test case to verify those values are present after unmarshaling.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.