-
Notifications
You must be signed in to change notification settings - Fork 619
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
Support Consul TLS #276
Comments
This change updates Fabio's configuration parameters to allow use and specification of TLS certificates for HTTPS. In Consul setups where full TLS is configured using CA private this allows Fabio to work in a secure manner. Closes fabiolb#276
I definitely need this as well. |
In my test environment, I had a very simple consul setup. But in my main environment where I was going to deploy fabio, consul is setup to be fully encrypting gossip and tls communications, which for fabio that means it won't work, at all. |
This change updates Fabio's configuration parameters to allow use and specification of TLS certificates for HTTPS. In Consul setups where full TLS is configured using CA private this allows Fabio to work in a secure manner. Closes fabiolb#276
This change updates Fabio's configuration parameters to allow use and specification of TLS certificates for HTTPS. In Consul setups where full TLS is configured using CA private this allows Fabio to work in a secure manner. Closes fabiolb#276
Fixes fabiolb#276, fabiolb#501 (fixes fabiolb#391)
@sethvargo Sorry if this got put to the backlog. Is this still something that's needed mainline in fabio? Sorry for asking a redundant question if this has already be covered elsewhere. |
Hello, need this too, deployment compromised. How can we help to see fabio able to connect to consul via TLS and TLS with client connect ? |
Currently only specifying the address is allowed, but there are many other options for Consul TLS like the CA file, key, and cert.
The text was updated successfully, but these errors were encountered: