envoyconfig: disable validation context when no client certificates are required #4151
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.
Summary
If a
ValidationContextType
is set for downstream TLS contexts, it will result in the server sending a client certificate request during the TLS handshake. This may prompt the user to choose a client certificate (though it doesn't always result in this behavior).This PR updates the code to only set the validation context if the global config requires a client certificate, or any of the routes do.
Related issues
Fixes #4150
Checklist
improvement
/bug
/ etc)