mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-30 02:51:07 +02:00
3701dcf3ca
* saving because laptop is bad and should feel bad * save * make supported login types partial * add api-docs partial * update custom login docs * reword tip? * add delete section * address feedback, update using a direct link section * move tips down * remove table lines and see if that fixes build? * revert changes to custom-messages mdx * add line break? * format fixes * empty commit again * check vercel? * add line break * update "namespace" to be "namespace_path" * reduce use of "preferred" * address feedback * use "settings" to match GUI verbiage * missed a couple feedback comments * add "single" and "multiple" * fix link rendering * fix namespace-path typos for namespace params referencing namespace context * address feedback --------- Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
45 lines
1.3 KiB
Plaintext
45 lines
1.3 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Token - Auth Methods
|
|
description: The token store auth method is used to authenticate using tokens.
|
|
---
|
|
|
|
# Token auth method
|
|
|
|
@include 'tips/custom-authn.mdx'
|
|
|
|
~> **NOTE:** The Token auth method cannot be configured with Vault's built-in [Login MFA](/vault/docs/auth/login-mfa) feature.
|
|
|
|
The `token` auth method is built-in and automatically available at `/auth/token`. It
|
|
allows users to authenticate using a token, as well to create new tokens, revoke
|
|
secrets by token, and more.
|
|
|
|
When any other auth method returns an identity, Vault core invokes the
|
|
token method to create a new unique token for that identity.
|
|
|
|
The token store can also be used to bypass any other auth method:
|
|
you can create tokens directly, as well as perform a variety of other
|
|
operations on tokens such as renewal and revocation.
|
|
|
|
Please see the [token concepts](/vault/docs/concepts/tokens) page dedicated
|
|
to tokens.
|
|
|
|
## Authentication
|
|
|
|
### Via the CLI
|
|
|
|
```shell-session
|
|
$ vault login token=<token>
|
|
```
|
|
|
|
### Via the API
|
|
|
|
The token is set directly as a header for the HTTP API. The header should be
|
|
either `X-Vault-Token: <token>` or `Authorization: Bearer <token>`.
|
|
|
|
## API
|
|
|
|
The Token auth method has a full HTTP API. Please see the
|
|
[Token auth method API](/vault/api-docs/auth/token) for more
|
|
details.
|