Update client count docs #13197
Closed
Update client count docs #13197
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Synced changes.
BrandonRomano
approved these changes
Nov 18, 2021
jweissig
requested review from
taoism4504
and removed request for
taoism4504
taoism4504
reviewed
Nov 18, 2021
|
|
||
| If you chose to use the [Token Auth Method](/docs/auth/token) without an identity to avoid driving up client count, always assign each token to a role and entity alias. HashiCorp recommends creating a [Token Role](/api-docs/auth/token#create-update-token-role) first, with allowable entity aliases and issuing your token with the appropriate [role and entity alias name](/api-docs/auth/token#create-token). This is the name that will uniquely identify the client, no matter how many tokens are issued. See more on entity alias below. | ||
| If you choose to use the [Token Auth Method](https://www.vaultproject.io/docs/auth/token) without an identity, a non-entity token, to avoid driving up client count, always assign each token to a role and entity alias. HashiCorp recommends creating a [Token Role](https://www.vaultproject.io/api-docs/auth/token#create-update-token-role) first, with allowable entity aliases and issuing your token with the appropriate [role and entity alias name](https://www.vaultproject.io/api-docs/auth/token#create-token). This is the name that will uniquely identify the client, no matter how many tokens are issued. Without this each token will be counted as a client instead. For further information, please refer to the changes reflected in the [1.9 release notes](https://www.vaultproject.io/docs/release-notes/1.9.0) or check out our [learn guide](https://learn.hashicorp.com/collections/vault/new-release). |
There was a problem hiding this comment.
Per engineering's markdown guidelines, please use absolute paths starting from the root when linking on the same site.
https://vaultproject.io/docs/auth/token -> /docs/auth/token
https://vaultproject.io/api-docs/auth/token/#create-update-token-role -> /api-docs/auth/token/#create-update-token-role
taoism4504
reviewed
Nov 18, 2021
taoism4504
approved these changes
Nov 18, 2021
Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com>
|
Closing in favour of: #16795 |
HridoyRoy
added a commit
that referenced
this pull request
Aug 24, 2022
* Docs: Client Count Concept clarity. Closes #12849 * Update website/content/docs/concepts/client-count/index.mdx * Docs: Client Count Concept clarity merged #13197 too. * Update website/content/docs/concepts/client-count/index.mdx Co-authored-by: Max Bowsher <maxbowsher@gmail.com> Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> Co-authored-by: Hridoy Roy <hridoyroy@berkeley.edu> Co-authored-by: Max Bowsher <maxbowsher@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Synced changes.