d1b3a63b2f
In some circumstances a consul 1.4 client could be running in an un-upgraded 1.3 or lower cluster. Currently this gives a 500 error on the new ACL token endpoint. Here we catch this specific 500 error/message and set the users AccessorID to null. Elsewhere in the frontend we use this fact (AccessorID being null) to decide whether to present the legacy or the new ACL UI to the user. Also: - Re-adds in most of the old style ACL acceptance tests, now that we are keeping the old style UI - Restricts code editors to HCL only mode for all `Rules` editing (legacy/'half legacy'/new style) - Adds a [Stop using] button to the old style ACL rows so its possible to logout. - Updates copy and documentation links for the upgrade notices
13 lines
736 B
Handlebars
13 lines
736 B
Handlebars
<p class="notice policy-management"><strong>Management</strong> This global-management token is built into Consul's policy system. You can apply this special policy to tokens for full access. This policy is not editable or removeable, but can be ignored by not applying it to any tokens. Learn more in our <a href="{{env 'CONSUL_DOCUMENTATION_URL'}}/guides/acl.html#builtin-policies" target="_blank" rel="noopener noreferrer">documentation</a>.</p>
|
|
<div>
|
|
<dl>
|
|
<dt>Name</dt>
|
|
<dd>{{item.Name}}</dd>
|
|
<dt>Valid Datacenters</dt>
|
|
<dd>{{ join ', ' (policy/datacenters item)}}</dd>
|
|
<dt>Description</dt>
|
|
<dd>{{item.Description}}</dd>
|
|
</dl>
|
|
</div>
|
|
{{token-list caption="Applied to the following tokens:" items=items}}
|