-
Notifications
You must be signed in to change notification settings - Fork 616
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vault CA Certificate #182
Comments
Traveling now. I'll have a look later |
magiconair
added a commit
that referenced
this issue
Nov 4, 2016
Use the DefaultConfig and the environment variable overrides of the Vault API when creating the client.
@calvinmorrow I think I'm not initializing the Vault client properly. I've pushed a change that might do what you need. Would be great if you could test it since I'm shooting from the hip. |
@magiconair Thanks. I can confirm your commit solves the issue. Fabio is now pulling certificates from Vault. |
Cool. I'll merge it. |
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there any way to specify a supplemental certificate authority file for connections to Vault? Our Vault is configured with a self-signed certificate and Fabio is throwing
x509: certificate signed by unknown authority
on connections to it.The Vault api vendor code looks like it uses the env var VAULT_CACERT but as far as I can tell only the VAULT_TOKEN and VAULT_ADDR are used by Fabio.
Other than adding that certificate to the list of Go's trusted root certs ... any way to get that connection to succeed? We're using the Docker image so I'd rather avoid monkey patching the trusted cert file if possible.
The text was updated successfully, but these errors were encountered: