- Warning. This KV has a lock session. You can edit KV's with lock sessions, but we recommend doing so with care, or not doing so at all. It may negatively impact the active node it's associated with. See below for more details on the Lock Session and see our documentation for more information. -
-
- Error
- {{fsm.state.context.error.message}}
-
- Error
- {{error.message}}
-
- {{#if this.value.Name}}
- {{#if (eq this.error.status '403')}}
- Consul login failed
- We received a token from your OIDC provider but could not log in to Consul
- with it.
- {{else if (eq this.error.status '401')}}
- Could not log in to provider
- The OIDC provider has rejected this access token. Please have an
- administrator check your auth method configuration.
- {{else if (eq this.error.status '499')}}
- SSO log in window closed
- The OIDC provider window was closed. Please try again.
- {{else}}
- Error
- {{this.error.detail}}
- {{/if}}
+
- The token entered does not exist. Please enter a valid token to log in.
- {{else if (eq this.error.status '404')}}
- No providers
- No SSO providers are configured for that Partition.
- {{else}}
- Error
- {{this.error.detail}}
- {{/if}}
+ Error
{{/if}}
-
- Cross-partition communication is not supported outside of the primary datacenter. You will only be able to select namespaces for source and destination services. -
-- This Intention is view only because it is managed through an Intention Custom Resource in your Kubernetes cluster. -
-- Some of your intentions are being managed through an Intention Custom Resource in your Kubernetes cluster. Those managed intentions will be view only in the UI. Any intentions created in the UI will work but will not be synced to the Custom Resource Definition (CRD) datastore. -
-
-
- {{t "components.consul.intention.notice.permissions.body"}} -
-
-
- {{t 'routes.dc.nodes.index.agentless.notice.body'}} -
-- 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 documentation. -
-- We have upgraded our ACL system by allowing you to create reusable policies which you can then apply to tokens. Don't worry, even though this token was written in the old style, it is still valid. However, we do recommend upgrading your old tokens to the new style. Learn how in our documentation. -
-We have upgraded our ACL System to allow the creation of reusable policies that can be applied to tokens. Read more about the changes and how to upgrade legacy tokens in our documentation.
-
-
- {{compute (fn route.t 'notice.${prop}.body' - (hash - prop=prop - ) - )}} -
-- These settings are immediately saved to local storage and persisted through browser usage. -
-