From a14a9a781f8eeb8d80989f383954efd5925b604d Mon Sep 17 00:00:00 2001 From: anxjok <112848167+anxjok@users.noreply.github.com> Date: Wed, 9 Aug 2023 15:33:09 +0200 Subject: [PATCH] clarify when a entity is created (#22233) * clarify when a entity is created * Create 22233.txt --------- Co-authored-by: Violet Hynes --- changelog/22233.txt | 3 +++ website/content/docs/secrets/identity/index.mdx | 2 +- 2 files changed, 4 insertions(+), 1 deletion(-) create mode 100644 changelog/22233.txt diff --git a/changelog/22233.txt b/changelog/22233.txt new file mode 100644 index 0000000000..f6b1a5c33a --- /dev/null +++ b/changelog/22233.txt @@ -0,0 +1,3 @@ +```release-note:improvement +docs: Clarify when a entity is created +``` diff --git a/website/content/docs/secrets/identity/index.mdx b/website/content/docs/secrets/identity/index.mdx index 5d50d6dd47..adad33220d 100644 --- a/website/content/docs/secrets/identity/index.mdx +++ b/website/content/docs/secrets/identity/index.mdx @@ -13,7 +13,7 @@ internally maintains the clients who are recognized by Vault. Each client is internally termed as an `Entity`. An entity can have multiple `Aliases`. For example, a single user who has accounts in both GitHub and LDAP, can be mapped to a single entity in Vault that has 2 aliases, one of type GitHub and one of -type LDAP. When a client authenticates via any of the credential backends +type LDAP. When a client authenticates successfully via any of the credential backends (except the Token backend), Vault creates a new entity and attaches a new alias to it, if a corresponding entity doesn't already exist. The entity identifier will be tied to the authenticated token. When such tokens are put to use, their