Skip to content
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

Clarification - What is acl_api_token? #505

Closed
spuder opened this issue Oct 12, 2019 · 1 comment
Closed

Clarification - What is acl_api_token? #505

spuder opened this issue Oct 12, 2019 · 1 comment

Comments

@spuder
Copy link
Contributor

spuder commented Oct 12, 2019

In the readme it says $acl_api_token can either be the boostrap token, or a dedicated token.

Here is an example to automatically create a policy and token for each host. For development environments acl_api_token can be the bootstrap token. For production it should be a dedicated token with access to write/read from the acls.

Can you provide an example of what an acl token with write/read to the acl's would look like?

I've created the following:

A 'Policy' named 'foo' with acl write permissions

  acl = "write"

A 'Token' named 'bar' with applied Policy 'foo' granting acl write permissions

I then take the secret ID of the Token 'bar', and apply it to the puppet variable $acl_api_token

However I find that puppet is unable to create policies and tokens.

@bmx0r
Copy link

bmx0r commented Jan 6, 2020

see: https://learn.hashicorp.com/consul/day-0/acl-guide
You can use the bootstrap token in step2 (Super admin token of consul) or you could create one token yourself taht will include a specific policy for "puppet" to limit what puppet can manage

@spuder spuder closed this as completed Apr 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants