Consul Token Support?

[brotherdust]

Hello and thank you very kindly for writing this software! I read through some of the source and it would appear that there's no support for using a token to connect to Consul, which would preclude the use of ACL's. It's possible I'm missing something, so just wanted to confirm that is the case before I try to find a workaround or inflicting my horrible code on anyone. =)

Thanks!

[mayuresh82]

Hello - Are you referring to the use of a token for reading from consul ? Could you point me to the consul documentation that refers to this ACL mechanism ?

[brotherdust]

Hello - Are you referring to the use of a token for reading from consul ? Could you point me to the consul documentation that refers to this ACL mechanism ?

Yes. After the ACL system is bootstrapped in Consul, a policy must be defined for a Consul client to have access (in this case, gocast). After an ACL is defined, a token is generated and attached to the policy. This token is presented by the client to Consul to authenticate itself; Consul then grants access to the paths specified by the policy that the token is attached to.

https://learn.hashicorp.com/tutorials/consul/access-control-setup-production

https://www.consul.io/docs/security/acl#acl-documentation

Enabling ACL is considered best-practice as part of securing access to a production Consul cluster.

[mayuresh82]

Thanks I will look into it.

[mayuresh82]

added via #17