42 lines
1.8 KiB
Markdown
42 lines
1.8 KiB
Markdown
|
---
|
||
|
layout: "docs"
|
||
|
page_title: "Identity Secret Backend"
|
||
|
sidebar_current: "docs-secrets-identity"
|
||
|
description: |-
|
||
|
The Identity secret backend for Vault manages client identities.
|
||
|
---
|
||
|
|
||
|
# Identity Secret Backend
|
||
|
|
||
|
Name: `identity`
|
||
|
|
||
|
The Identity secret backend is the identity management solution for Vault. It
|
||
|
internally maintains the clients who are recognized by Vault. Each client is
|
||
|
internally termed as an `Entity`. An entity can have multiple `Personas`. 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 personas, one of type Github and one of
|
||
|
type LDAP. When a client authenticates via any of the credential backend
|
||
|
(except the Token backend), Vault creates a new entity and attaches a new
|
||
|
persona to it, if an entity doesn't already exist. The entity identifier will
|
||
|
be tied to the authenticated token. When such tokens are put to use, their
|
||
|
entity identifiers are audit logged, marking a trail of actions performed by
|
||
|
specific users.
|
||
|
|
||
|
Identity store allows operators to **manage** the entities in Vault. Entities
|
||
|
can be created and personas can be tied to entities, via the ACL'd API. There
|
||
|
can be policies set on the entities which adds capabilities to the tokens that
|
||
|
are tied to entity identiers. The capabilities granted to tokens via the
|
||
|
entities are **an addition** to the existing capabilities of the token and
|
||
|
**not** a replacement. Note that the additional capabilities of the token that
|
||
|
get inherited from entities are computed at request time. This provides
|
||
|
flexibility in controlling the access of tokens that are already issued.
|
||
|
|
||
|
This backend will be mounted by default. This backend cannot be unmounted or
|
||
|
remounted.
|
||
|
|
||
|
## API
|
||
|
|
||
|
The Identity secret backend has a full HTTP API. Please see the
|
||
|
[Identity secret backend API](/api/secret/identity/index.html) for more
|
||
|
details.
|