github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Adjust the ACLs requirement section wording and add link to ACL docs 

It's better to avoid the ambiguous Vault statement that was not clarified and drop the loaded "roles" term in favor of "capabilities" since the ACL system is described as capability-based in previous ACL documentation.
pull/9106/head
Kent 'picat' Gruber 2020-11-06 16:25:21 -05:00
parent facd48b486
commit 81efada5c3
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
website/pages/docs/security/security-models/core.mdx
View File

@ -151,12 +151,11 @@ environment and adapt these configurations accordingly.
using the local Consul agent. In this case ACLs should be enabled to provide authorization and only ACL tokens would
need to be distributed.
- **ACLs** - The access control list (ACL) system provides a capability-based control mechanism for Consul
administrators to define scoped, custom roles (typically within Vault) tied to an individual human, or machine
operator identity. To ultimately secure the ACL system, administrators should configure the
[`default_policy`](/docs/agent/options#acl_default_policy) to "deny".
- **ACLs** - The access control list (ACL) system provides a security mechanism for Consul administrators to grant
capabilities tied to an individual human, or machine operator identity. To ultimately secure the ACL system,
administrators should configure the [`default_policy`](/docs/agent/options#acl_default_policy) to "deny".
The system is comprised of five major components:
The [system](/docs/acl/acl-system) is comprised of five major components:
- **🗝 Token** - API key associated with policies, roles, or service identities.