mirror of
https://github.com/status-im/consul.git
synced 2025-01-11 06:16:08 +00:00
/docs/security/acl
This commit is contained in:
parent
8a58aab610
commit
6c0f27f427
@ -1,8 +1,8 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: ACL in Federated Datacenters
|
||||
page_title: ACLs for Federated Datacenters
|
||||
description: >-
|
||||
This topic describes the specific ACL bootstrapping policies that are necessary when ACLs are enabled for federated, multi-datacenter deployments.
|
||||
You can apply ACLs in federated datacenters to secure access for distributed deployments. Learn how to create replication tokens from agent tokens and apply them to server and client agents.
|
||||
---
|
||||
|
||||
# ACLs in Federated Datacenters
|
||||
|
@ -1,11 +1,8 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: ACL System (Legacy Mode)
|
||||
page_title: Legacy ACL System
|
||||
description: >-
|
||||
Consul provides an optional Access Control List (ACL) system which can be used
|
||||
to control access to data and APIs. The ACL system is a Capability-based
|
||||
system that relies on tokens which can have fine grained rules applied to
|
||||
them. It is very similar to AWS IAM in many ways.
|
||||
Consul's original ACL system was updated in version 1.4.0 and the legacy system is no longer supported as of 1.11.0. Learn how Consul's original ACLs worked and how it differs from current ACLs.
|
||||
---
|
||||
|
||||
# ACL System in Legacy Mode
|
||||
|
@ -1,13 +1,8 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: ACL Token Migration
|
||||
page_title: Token Migration (ACL)
|
||||
description: >-
|
||||
Consul 1.4.0 introduces a new ACL system with improvements for the security
|
||||
and
|
||||
|
||||
management of ACL tokens and policies. This guide documents how to upgrade
|
||||
|
||||
existing (now called "legacy") tokens after upgrading to 1.4.0.
|
||||
Migrate legacy tokens when updating to Consul 1.4.0+ from earlier versions to use the improved ACL system. Learn about the migration process, how to update tokens, and examples for creating policies.
|
||||
---
|
||||
|
||||
# ACL Token Migration
|
||||
|
@ -2,10 +2,10 @@
|
||||
layout: docs
|
||||
page_title: ACL Policies
|
||||
description: >-
|
||||
This topic describes policies as used in Consul's access control list (ACL) system. A policy is a group of one or more ACL rules that define which services and agents are authorized to communicate with other resources in the network.
|
||||
Policies are groups of one or more rules that link resources to access permissions and tokens in the ACL system. Learn how to format and combine rules into policies and implement policies in Consul.
|
||||
---
|
||||
|
||||
# Policies
|
||||
# ACL Policies
|
||||
|
||||
This topic describes policies, which are components in Consul's access control list (ACL) system. Policies define which services and agents are authorized to interact with resources in the network.
|
||||
|
||||
|
@ -1,12 +1,11 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Roles
|
||||
page_title: ACL Roles
|
||||
description: >-
|
||||
This topic describes roles within the access control list (ACL) system. A role is a named set of policies and service identities.
|
||||
They enable you to reuse policies by decoupling the policies from the token distributed to team members.
|
||||
Roles are a collection of ACL policies that enable service and node identities. Learn how roles allow you to reuse and update policies without requiring unique tokens for each requestor.
|
||||
---
|
||||
|
||||
# Roles
|
||||
# ACL Roles
|
||||
|
||||
A role is a collection of policies that your ACL administrator can link to a token.
|
||||
They enable you to reuse policies by decoupling the policies from the token distributed to team members.
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: ACL Rules Reference
|
||||
page_title: ACL Rules
|
||||
description: >-
|
||||
This topic provides reference information for the types of access control level (ACL) rules you can create and how they affect access to datacenter resources.
|
||||
Rules define read, write, and deny access for datacenter resources. Learn about these resources and how to assign rules to them, as well as their restrictions and API interactions.
|
||||
---
|
||||
|
||||
# Rules Reference
|
||||
# ACL Rules
|
||||
|
||||
This topic provides reference information for the types of access control list (ACL) rules you can create and how they affect access to datacenter resources. For details on how to create rules and group them into policies, see [Policies](/docs/security/acl/acl-policies).
|
||||
|
||||
|
@ -1,11 +1,11 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Tokens
|
||||
page_title: ACL Tokens
|
||||
description: >-
|
||||
This topic describes access control list (ACL) tokens. Tokens are the core method of authentication in Consul.
|
||||
Tokens authenticate users, services, and agents in Consul’s ACL system. Learn about token attributes, special-purpose and built-in tokens, and how to pass a token’s SecretID in the CLI and API.
|
||||
---
|
||||
|
||||
# Tokens
|
||||
# ACL Tokens
|
||||
|
||||
This topic describes access control list (ACL) tokens, which are the core method of authentication in Consul.
|
||||
|
||||
|
@ -1,8 +1,8 @@
|
||||
---
|
||||
layout: docs
|
||||
page_title: Access Control List (ACL) Overview
|
||||
page_title: Access Control List (ACL): Overview
|
||||
description: >-
|
||||
This topic describes provides an overview of the optional access control list (ACL) system shipped with Consul. The ACL system authenticates requests and authorizes access to resources. It is used by the UI, API, and CLI for service-to-service communication and agent-to-agent communication.
|
||||
Consul's ACL system secures communication and controls access to the API, CLI, and UI. Learn about ACL components and how they interact to authenticate requests and authorize access for your network.
|
||||
---
|
||||
|
||||
# Access Control List (ACL) Overview
|
||||
|
Loading…
x
Reference in New Issue
Block a user