-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add Flag to disable cert check #67
Comments
@mkohn Trying to clarify your use case a little further. Is there something pushing you to use self-signed certificates and HTTPS? There are a few secure ways outside of the app that I've typically seen followed in dev environments, such as trusting the cert in your client(s) or switching to a published port+http over the localhost loopback. It's not impossible to disable the cert verification but given the security implications I'd love to have a use case to point to. |
@taiidani for our ephemeral dev Jenkins environments we are using self-signed certs but still leave the Jenkins service to only communicating over HTTPs. We are testing Terraform to provision and maintain our jenkins jobs. |
Hmm -- I'm still not following as to why you're not trusting the self-signed cert in your clients to avoid the MITM attack vulnerability, but I can see that starting out a dev environment you might want to begin with the [much] easier route of turning off certificate verification. I'll tag this in for our 0.10 release 👍 |
Stale issue message |
Stale issue message |
Having a hard time allocating free time to configure this and test it appropriately to ensure stability, but it's still a valid request. Reopening issue. |
Stale issue message |
Any workaround for it? |
I assume you can add your self signed cert into CA storage on a server where you apply terraform from. |
For some dev environments, a valid SSL cert might not be setup, it would be nice to be able to disable the Cert Validation Check to not get
x509: certificate signed by unknown authority
and terraform to fail.The text was updated successfully, but these errors were encountered: