Tim Gross bf67f53ba2 docs: add note about Consul Enterprise role bindings and namespaces (#25426) ...

When configuring Consul to use Nomad workload identities, you create the Consul
auth method in the default namespace. If you're using Consul Enterprise
namespaces, there are two available approaches: one is to create the tokens in
the default namespace and give them policies that define cross-namespace access,
and the other is to use binding rules that map the login to a particular
namespace. The latter is what we show in our docs, but this was missing a note
that any roles (and their associated policies) targetted by `-bind-type role`
need to exist in the Consul namespace we're logging into.

Also, in Nomad CE, the `consul.namespace` flag is always treated as having been set to
`"default"`. That is, we ignore it and don't return an error even though it's a
Nomad ENT-only feature. Clarify this in the documentation for the field the same
way we've done for the `cluster` field.

Co-authored-by: Aimee Ukasick <aimee.ukasick@hashicorp.com>

2025-03-18 15:35:00 -04:00

..

consul

docs: add note about Consul Enterprise role bindings and namespaces (#25426)

2025-03-18 15:35:00 -04:00

vault

vault: Remove legacy token based authentication workflow. (#25155)

2025-02-28 07:40:02 +00:00

index.mdx

feat(website): migrates to new nav data format (#10264)

2021-03-31 08:43:17 -05:00