consul.tls ca, cert and key options should be optional

[bitsofinfo]

What did you do?

Attempt to connect traefik to a consul endpoint running TLS that presents a legit CA signed SSL certificate.

I have no need to present my own certificate when connecting to consul as a client over TLS. Other tools support this fine, such as https://github.com/hashicorp/consul-template

[consul]
  endpoint = "myconsul.mydomain.com:8501" # SSL port
  watch = true
  prefix = "traefik-stage"

[consul.tls]

What did you expect to see?

Traefik should be able to connect via SSL to a consul backend presenting a legit CA signed SSL certificate without issue.

I should not have to specify the ca, cert, and key options

What did you see instead?

2017-06-08T16:23:17.882619269Z 2017/06/08 16:23:17 Error creating kv store: Failed to load TLS keypair: tls: failed to find any PEM data in certificate input

Output of traefik version: (What version of Traefik are you using?)

Traefik version v1.3.0 built on 2017-05-31_05:48:42PM

What is your environment & configuration (arguments, toml, provider, platform, ...)?

relevant TOML config section

.....
[consul]
  endpoint = "myconsul.mydomain.com:8501" SSL port
  watch = true
  prefix = "traefik-stage"

[consul.tls]

If applicable, please paste the log output in debug mode (--debug switch)

see above

[bitsofinfo]

My setup authenticates to consul not via client certs, but via acl token, which also could use a config option as noted in #1717

[nmengin]

We have to check into libkv if this behavior is enabled.

[p3sa]

Hi @bitsofinfo I had the same issue while using the consul catalog provider, I haven't tested it out but if you prepend https:// to the endpoint value in your configuration it should work

[bitsofinfo]

@p3sa I verified this works, might clarify this in the docs

[ldez]

I'll close this issue, because I think the question is answered, but feel free to continue the conversation.