Add support for Non-Default CA files using ssl_ca_file#67214
Draft
stephen-bracken wants to merge 1 commit into
Draft
Add support for Non-Default CA files using ssl_ca_file#67214stephen-bracken wants to merge 1 commit into
stephen-bracken wants to merge 1 commit into
Conversation
stephen-bracken
force-pushed
the
ssl-ca-file
branch
9 times, most recently
from
53ca484 to
52d8194
Compare
stephen-bracken
force-pushed
the
ssl-ca-file
branch
from
52d8194 to
ea5debb
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
1 participant
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 support for Non-Default CA files using ssl_ca_file
When using mTLS for the execution api, certificate verification fails if the CA for the certificate is not loaded into the ssl context. By specifying the CA using
--ssl_ca_file(or[api] ssl_ca_filein the config), the required root certificate can be specified.Was generative AI tooling used to co-author this PR?