* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
4.7 KiB
layout | page_title | sidebar_title | sidebar_current | description |
---|---|---|---|---|
docs | token create - Command | create | docs-commands-token-create | The "token create" command creates a new token that can be used for authentication. This token will be created as a child of the currently authenticated token. The generated token will inherit all policies and permissions of the currently authenticated token unless you explicitly define a subset list policies to assign to the token. |
token create
The token create
command creates a new token that can be used for
authentication. This token will be created as a child of the currently
authenticated token. The generated token will inherit all policies and
permissions of the currently authenticated token unless you explicitly define a
subset list policies to assign to the token.
A ttl can also be associated with the token. If a ttl is not associated with the token, then it cannot be renewed. If a ttl is associated with the token, it will expire after that amount of time unless it is renewed.
Metadata associated with the token (specified with -metadata
) is written to
the audit log when the token is used.
If a role is specified, the role may override parameters specified here.
Examples
Create a token attached to specific policies:
$ vault token create -policy=my-policy -policy=other-policy
Key Value
--- -----
token 95eba8ed-f6fc-958a-f490-c7fd0eda5e9e
token_accessor 882d4a40-3796-d06e-c4f0-604e8503750b
token_duration 768h
token_renewable true
token_policies [default my-policy other-policy]
Create a periodic token:
$ vault token create -period=30m
Key Value
--- -----
token fdb90d58-af87-024f-fdcd-9f95039e353a
token_accessor 4cd9177c-034b-a004-c62d-54bc56c0e9bd
token_duration 30m
token_renewable true
token_policies [my-policy]
Usage
The following flags are available in addition to the standard set of flags included on all commands.
Output Options
-
-field
(string: "")
- Print only the field with the given name. Specifying this option will take precedence over other formatting directives. The result will not have a trailing newline making it ideal for piping to other processes. -
-format
(string: "table")
- Print the output in the given format. Valid formats are "table", "json", or "yaml". This can also be specified via theVAULT_FORMAT
environment variable.
Command Options
-
-display-name
(string: "")
- Name to associate with this token. This is a non-sensitive value that can be used to help identify created secrets (e.g. prefixes). -
-explicit-max-ttl
(duration: "")
- Explicit maximum lifetime for the token. Unlike normal TTLs, the maximum TTL is a hard limit and cannot be exceeded. This is specified as a numeric string with suffix like "30s" or "5m". -
-id
(string: "")
- Value for the token. By default, this is an auto-generated value. Specifying this value requires sudo permissions. -
-metadata
(k=v: "")
- Arbitrary key=value metadata to associate with the token. This metadata will show in the audit log when the token is used. This can be specified multiple times to add multiple pieces of metadata. -
-no-default-policy
(bool: false)
- Detach the "default" policy from the policy set for this token. -
-orphan
(bool: false)
- Create the token with no parent. This prevents the token from being revoked when the token which created it expires. Setting this value requires sudo permissions. -
-period
(duration: "")
- If specified, every renewal will use the given period. Periodic tokens do not expire (unless-explicit-max-ttl
is also provided). Setting this value requires sudo permissions. This is specified as a numeric string with suffix like "30s" or "5m". -
-policy
(string: "")
- Name of a policy to associate with this token. This can be specified multiple times to attach multiple policies. -
-renewable
(bool: true)
- Allow the token to be renewed up to it's maximum TTL. -
-role
(string: "")
- Name of the role to create the token against. Specifying -role may override other arguments. The locally authenticated Vault token must have permission forauth/token/create/<role>
. -
-ttl
(duration: "")
- Initial TTL to associate with the token. Token renewals may be able to extend beyond this value, depending on the configured maximumTTLs. This is specified as a numeric string with suffix like "30s" or "5m". -
-use-limit
(int: 0)
- Number of times this token can be used. After the last use, the token is automatically revoked. By default, tokens can be used an unlimited number of times until their expiration.