mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-10-29 17:52:32 +00:00
clarify when a entity is created (#22233)
* clarify when a entity is created * Create 22233.txt --------- Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
This commit is contained in:
3
changelog/22233.txt
Normal file
3
changelog/22233.txt
Normal file
@@ -0,0 +1,3 @@
|
||||
```release-note:improvement
|
||||
docs: Clarify when a entity is created
|
||||
```
|
||||
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user