status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

renamed acl-overview to index, fixed formatting, reworded node/service ID intros

This commit is contained in:
trujillo-adam 2022-03-01 10:03:22 -08:00
parent 4331a29f95
commit e9a42df7c7
4 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -70,7 +70,9 @@ Roles may contain the following table describe the attributes:
<!-- -> Added in Consul 1.5.0 # Remove and lean on versioning?-->
You can specify a service identity when configuring roles or linking tokens to policies. Service identities are used during the authorization process to automatically generate a policy for the service(s) specifed. The policy will be linked to the role or token so that the service(s) can _be discovered_ and _discover other healthy service instances_ in a service mesh. See [Service Mesh](/docs/connect) for additional information about Consul service mesh. Service identities enable you to quickly construct policies for services, rather than creating identical polices for each service.
You can specify a service identity when configuring roles or linking tokens to policies. Service identities enable you to quickly construct policies for services, rather than creating identical polices for each service.
Service identities are used during the authorization process to automatically generate a policy for the service(s) specifed. The policy will be linked to the role or token so that the service(s) can _be discovered_ and _discover other healthy service instances_ in a service mesh. Refer to the [service mesh](/docs/connect) topic for additional information about Consul service mesh.
### Service Identity Specification
@ -242,9 +244,9 @@ node_prefix "" {
<!-- -> Added in Consul 1.8.1 -- remove and lean on doc version? -->
You can specify a node identity when configuring roles or linking tokens to policies. Node identities are used during the authorization process to automatically generate a policy for the node(s) specifed. In most cases, "node" refers to a Consul agent.
You can specify a node identity when configuring roles or linking tokens to policies. _Node_ commonly refers to a Consul agent, but a node can also be a physical server, cloud instance, virtual machine, or container.
You can specify the token linked to the policy in the [`acl_tokens_agent`](/docs/agent/options#acl_tokens_agent) field when configuring the agent. Node identities enable you to quickly construct policies for nodes, rather than creating identical polices for each node.
Node identities enable you to quickly construct policies for nodes, rather than manually creating identical polices for each node. They are used during the authorization process to automatically generate a policy for the node(s) specifed. You can specify the token linked to the policy in the [`acl_tokens_agent`](/docs/agent/options#acl_tokens_agent) field when configuring the agent.
### Node Identity Specification

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

@ -106,7 +106,7 @@ In the following example, the agent is configured to use a default token:
</CodeTabs>
Refer to the [agent configurations documentation]() for additional information.
Refer to the [agent configurations documentation](/docs/agent/options) for additional information.
### Command Line Requests

0
website/content/docs/security/acl/acl-system.mdx → website/content/docs/security/acl/index.mdx
View File

2
website/data/docs-nav-data.json
View File

@ -868,7 +868,7 @@
"routes": [
{
"title": "ACL System Overview",
"path": "security/acl/acl-system"
"path": "security/acl"
},
{
"title": "Tokens",