Skip to content
This repository was archived by the owner on May 6, 2022. It is now read-only.

Add broker-specific control for insecure communications #848

Closed
pmorie opened this issue May 13, 2017 · 1 comment
Closed

Add broker-specific control for insecure communications #848

pmorie opened this issue May 13, 2017 · 1 comment
Labels
Milestone

Comments

@pmorie
Copy link
Contributor

pmorie commented May 13, 2017

Currently, we hard-code the InsecureSkipVerify option on the TLS config for the broker client's HTTP transport to allow communicating with brokers who do not have a root-signed certificate. We probably need to retain this capability, but it should be broker-specific. Something like:

type BrokerSpec struct {
  Insecure *bool
}
@pmorie pmorie added the api label May 13, 2017
@pmorie pmorie added this to the 1.0.0 milestone May 13, 2017
@pmorie
Copy link
Contributor Author

pmorie commented May 13, 2017

Oops, this is a dupe of #606

@pmorie pmorie closed this as completed May 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant