Skip to content
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

Closed
calvinmorrow opened this issue Nov 3, 2016 · 5 comments
Closed

Vault CA Certificate #182

calvinmorrow opened this issue Nov 3, 2016 · 5 comments
Labels
Milestone

Comments

@calvinmorrow
Copy link

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.

@magiconair
Copy link
Contributor

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.
@magiconair
Copy link
Contributor

@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.

@calvinmorrow
Copy link
Author

@magiconair Thanks. I can confirm your commit solves the issue. Fabio is now pulling certificates from Vault.

@magiconair
Copy link
Contributor

Cool. I'll merge it.

@magiconair magiconair added the bug label Nov 4, 2016
@magiconair
Copy link
Contributor

Merged to master.

@magiconair magiconair added this to the 1.3.5 milestone Nov 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants