luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

website: Use secret id instead of policy id (#5049) 

The document uses _the agent-token policy_ as agent token by mistake.
So I fixed it to use the secret id instead of it.
This commit is contained in:
Junpei Tsuji 2019-01-04 00:45:01 +09:00 committed by Matt Keeler
parent c723ba09d5
commit 6f14d3eeae
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/docs/guides/acl.html.md
View File

@ -361,7 +361,7 @@ with a configuration file that enables ACLs:
"default_policy" : "deny",
"down_policy" : "extend-cache",
"tokens" : {
"agent" : "fcd68580-c566-2bd2-891f-336eadc02357"
"agent" : "da666809-98ca-0e94-a99c-893c4bf5f9eb"
}
}
}
@ -371,7 +371,7 @@ Similar to the previous example, in Consul 0.9.1 and later you can also introduc
agent token using an API, so it doesn't need to be set in the configuration file:
```bash
$ consul acl set-agent-token agent "fcd68580-c566-2bd2-891f-336eadc02357"
$ consul acl set-agent-token agent "da666809-98ca-0e94-a99c-893c4bf5f9eb"
ACL token "agent" set successfully
```
@ -406,7 +406,7 @@ If we supply the token we created above we will be able to see a listing of node
it has write privileges to an empty `node` prefix, meaning it has access to all nodes:
```bash
$ CONSUL_HTTP_TOKEN=fcd68580-c566-2bd2-891f-336eadc02357 consul members
$ CONSUL_HTTP_TOKEN=da666809-98ca-0e94-a99c-893c4bf5f9eb consul members
Node Address Status Type Build Protocol DC
node-1 127.0.0.1:8301 alive server 0.9.0dev 2 dc1
node-2 127.0.0.2:8301 alive client 0.9.0dev 2 dc1