Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vault documentation: Update note about tokens #13351

Merged
merged 1 commit into from
Dec 7, 2021
Merged

Vault documentation: Update note about tokens #13351

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions website/content/docs/concepts/tokens.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@ description: Tokens are a core auth method in Vault. Concepts and important feat

# Tokens

!> **Warning**: Since tokens are considered opaque values, their structure is undocumented and subject to change. For these reasons, we do not recommend using tokens within your scripts or for automation since it can cause breakage.

Tokens are the core method for _authentication_ within Vault. Tokens
can be used directly or [auth methods](/docs/concepts/auth)
can be used to dynamically generate tokens based on external identities.
Expand All @@ -27,9 +29,6 @@ holder is allowed to do within Vault. Other mapped information includes
metadata that can be viewed and is added to the audit log, such as creation
time, last renewal time, and more.

~> Note that external to Vault, tokens are to be considered opaque values
by users and as such, their structure is both currently undocumented and
subject to change.

Read on for a deeper dive into token concepts.

Expand Down