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

Apply suggestions from code review 

Co-authored-by: mrspanishviking <kcardenas@hashicorp.com>
This commit is contained in:
trujillo-adam 2022-03-08 16:02:59 -08:00 committed by GitHub
parent ed8aa7d24a
commit 4e7dc7ce91
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/security/acl/acl-policies.mdx
View File

@ -113,7 +113,7 @@ Use the `policy` keyword and one of the following access levels to set a policy
- `write`: Allows the resource to be read and modified.
- `deny`: Denies read and write access to the resource.
The special `list` access level provides access to all keys with the specified resource label in the Consul KV. The `list` access level can only be used with the `key_prefix` resource. The [`acl.enable_key_list_policy`](/docs/agent/options#acl_enable_key_list_policy) setting must be set to `true`.
The special `list` access level provides access to all keys with the specified resource label in the [Consul KV](/commands/kv/). The `list` access level can only be used with the `key_prefix` resource. The [`acl.enable_key_list_policy`](/docs/agent/options#acl_enable_key_list_policy) setting must be set to `true`.
### Matching and Prefix Values

6
website/content/docs/security/acl/acl-roles.mdx
View File

@ -42,7 +42,7 @@ Issue the `consul acl role create` command to create roles. In the following exa
$ consul acl role create -name "crawler" -description "web crawler role" -policy-name "crawler-kv" -policy-name "crawler-key"
```
Refer to the [command line documentation](/command/acl/role) for details.
Refer to the [command line documentation](/commands/acl/role) for details.
### API
@ -56,7 +56,7 @@ Refer to the [API documentation](/api-docs/acl/roles) for details.
## Role Attributes
Roles may contain the following table describe the attributes:
Roles may contain the following attributes:
- `ID`: The `ID` is an auto-generated public identifier. You can specify the role `ID` when linking it to tokens.
- `Name`: A unique meaningful name for the role. You can specify the role `Name` when linking it to tokens.
@ -277,7 +277,7 @@ NodeIdentities = {
</CodeTabs>
- `NodeIdentities`: Declares a node identity block.
- `NodeIdentities.ServiceName`: String value that specifies the name of the node you want to associate with the policy.
- `NodeIdentities.NodeName`: String value that specifies the name of the node you want to associate with the policy.
- `NodeIdentitites.Datacenters`: Array that specifies the names of datacenters in which the node identity applies. This field is optional.
Refer to the the [API documentation for roles](/api/acl/roles#sample-payload) for additional information and examples.

2
website/content/docs/security/acl/acl-tokens.mdx
View File

@ -19,7 +19,7 @@ Refer to the [ACL system workflow overview](/docs/security/acl/acl-system#workfl
The person responsible for administrating ACLs can use the API or CLI to create and link tokens to entities that enable permissions to resources.
Refer to the [ACL API](/api-docs/acl) and [ACL CLI](/commands/acl) documentation for instructions on how to create and link tokens. Tokens can also be created dynamically from trusted external system using an
[auth method](/docs/security/acl/auth-methods).
[auth method](/docs/security/acl/auth-methods). Additionally, a tutorial is available to help you get started with creating tokens. Visit the the [Secure Consul with Access Control Lists (ACLs) tutorial](https://learn.hashicorp.com/tutorials/consul/access-control-setup-production?in=consul/security) to learn more through an interactive sandbox environment.
## Passing Tokens