scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-11-01 11:08:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

clarify when a entity is created (#22233)

Browse Source 
* clarify when a entity is created

* Create 22233.txt

---------

Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
This commit is contained in:
anxjok
2023-08-09 15:33:09 +02:00
committed by GitHub
parent d4e402d597
commit a14a9a781f
2 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
changelog/22233.txt Normal file
View File

@@ -0,0 +1,3 @@
```release-note:improvement
docs: Clarify when a entity is created
```

2
website/content/docs/secrets/identity/index.mdx
View File

@@ -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 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 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 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 (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 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 be tied to the authenticated token. When such tokens are put to use, their