mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
0660ea6fac
* Update README Let contributors know that docs will now be located in UDR * Add comments to each mdx doc Comment has been added to all mdx docs that are not partials * chore: added changelog changelog check failure * wip: removed changelog * Fix content errors * Doc spacing * Update website/content/docs/deploy/kubernetes/vso/helm.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> --------- Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
48 lines
1.7 KiB
Plaintext
48 lines
1.7 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Token - Auth Methods
|
|
description: The token store auth method is used to authenticate using tokens.
|
|
---
|
|
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
|
|
|
|
# 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.
|