Consul CLI login using Consul Secrets engine token from Vault

Consul
,
1

Hello,

I’m testing out Consul ACL with Vault integration.

I successfully integrated Consul authentication with a token generated from Vault, which works file in the UI. However, I’m unable to log in to Consul CLI using the token as I can’t find any documentation relating to Vault. Even the auth-methods#supported-types don’t list Vault as an option.

Is this not possible? If so do I need to manually create CLI token directly in the Consul server just so I can use the CLI?

Any help regarding this is appreciated as my only option at the moment is to leave the Consul server unprotected as I’m running into Coordinate update blocked by ACLs: accessorID="anonymous token" error from all client nodes.

Thanks

1 Like
2

Hi @praveenprem,

If you’ve generated a Consul token via Vault, you can use it directly in the CLI client to authenticate to Consul.

$ export CONSUL_HTTP_TOKEN=<Consul token from Vault>
$ consul members
…

# or
$ consul members -token=<Consul token from Vault>
3

Thanks, Blake that worked.

I was trying to us the consul login command which requires a method to be defined and that’s where I was going wrong

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.