Documentation updates for use with a private CA #774
Merged
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.
Hello!
Summary
I'm hoping to add a bit of documentation around using the
verify
parameter when initializing a client.The use case I'm working with, is we are only using a private CA to provide trust. The actual authentication is done through another channel (AWS IAM).
My understanding of the
cert
parameter, is to address the former, where the client provides its own certificate to authenticate with Vault.Validation
To validate this works as expected, here's a snippet of code in use with our system:
Using this code, the connection to Vault is only trusted if signed by our internal CA root certificate. The code snippet added in the documentation is the same flow, simply more generic