|
|
|
@ -579,11 +579,18 @@ Since clients now resolve ACLs locally, the [`acl_down_policy`](/docs/agent/opti
|
|
|
|
|
now applies to Consul clients as well as Consul servers. This will determine what the
|
|
|
|
|
client will do in the event that the servers are down.
|
|
|
|
|
|
|
|
|
|
Consul clients *do not* need to have the [`acl_master_token`](/docs/agent/options.html#acl_agent_master_token)
|
|
|
|
|
or the [`acl_datacenter`](/docs/agent/options.html#acl_datacenter) configured. They will
|
|
|
|
|
contact the Consul servers to determine if ACLs are enabled. If they detect that ACLs are
|
|
|
|
|
not enabled, they will check at most every 2 minutes to see if they have become enabled, and
|
|
|
|
|
will start enforcing ACLs automatically.
|
|
|
|
|
Consul clients must have [`acl_datacenter`](/docs/agent/options.html#acl_datacenter) configured
|
|
|
|
|
in order to enable agent-level ACL features. If this is set, the agents will contact the Consul
|
|
|
|
|
servers to determine if ACLs are enabled at the cluster level. If they detect that ACLs are not
|
|
|
|
|
enabled, they will check at most every 2 minutes to see if they have become enabled, and will
|
|
|
|
|
start enforcing ACLs automatically. If an agent has an `acl_datacenter` defined, operators will
|
|
|
|
|
need to use the [`acl_agent_master_token`](/docs/agent/options.html#acl_agent_master_token) to
|
|
|
|
|
perform agent-level operations if the Consul servers aren't present (such as for a manual join
|
|
|
|
|
to the cluster), unless the [`acl_down_policy`](/docs/agent/options.html#acl_down_policy) on the
|
|
|
|
|
agent is set to "allow".
|
|
|
|
|
|
|
|
|
|
Non-server agents do not need to have the [`acl_master_token`](/docs/agent/options.html#acl_agent_master_token)
|
|
|
|
|
configured; it is not used by agents in any way.
|
|
|
|
|
|
|
|
|
|
#### New ACL Policies
|
|
|
|
|
|
|
|
|
|