Skip to content

Commit

Permalink
backport of commit a78d535 (#28721)
Browse files Browse the repository at this point in the history
Co-authored-by: Adrian Todorov <[email protected]>
  • Loading branch information
hc-github-team-secure-vault-core and sofixa authored Oct 16, 2024
1 parent 784cad2 commit d7bfa41
Showing 1 changed file with 11 additions and 5 deletions.
16 changes: 11 additions & 5 deletions website/content/partials/faq/client-count/computing-clients.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,12 +50,18 @@ details.

### Does the Nomad-Vault integration affect client counts? ((#nomad))

**Maybe**.
**Yes**.

The [Nomad Vault integration](/nomad/docs/integrations/vault-integration)
uses either Workload Identity (JWT) or token roles for client count:

[Nomad Vault integration](/nomad/docs/integrations/vault-integration#token-role-based-integration)
uses token roles where a single token role creates tokens for many Nomad jobs.
Unless you have configured explicit identity aliases for your Nomad tokens,
Vault will record every running instance of a Nomad job as a unique client.
- Vault bases Workload Identity client counts on the
[`user_claim`](/vault/api-docs/auth/jwt#user_claim) field. The
recommended default is `nomad_job`, which results in 1 client per
Nomad job.
- Nomad deprecated token roles and will remove the feature in v1.10. Client
counts for legacy token roles treat each unique policy combination as 1
non-entity client.

### Are batch tokens counted differently than service tokens? ((#batch-tokens))

Expand Down

0 comments on commit d7bfa41

Please sign in to comment.