This removes all references I could find to: - credential provider - authentication backend - authentication provider - auth provider - auth backend in favor of the unified: - auth method
1.1 KiB
layout | page_title | sidebar_current | description |
---|---|---|---|
docs | Token - Auth Methods | docs-auth-token | The token store auth method is used to authenticate using tokens. |
Token Auth Method
The token
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 page dedicated to tokens.
Authentication
Via the CLI
$ vault login token=<token>
Via the API
The token is set directly as a header for the HTTP API. The name of the header should be "X-Vault-Token" and the value should be the token.
API
The Token auth method has a full HTTP API. Please see the Token auth method API for more details.