vault operator generate-root

Generates a new root token by combining a quorum of share holders. Must provide either '-otp' or '-pgp-key'

Options

NameDescription
--help, -hDisplay help
-address <string>Address of the Vault server. The default is https://127.0.0.1:8200. This can also be specified via the VAULT_ADDR environment variable
-agent-address <string>Address of the Agent. This can also be specified via the VAULT_AGENT_ADDR environment variable
-ca-cert <string>Path on the local disk to a single PEM-encoded CA certificate to verify the Vault server's SSL certificate. This takes precedence over -ca-path. This can also be specified via the VAULT_CACERT environment variable
-ca-path <string>Path on the local disk to a directory of PEM-encoded CA certificates to verify the Vault server's SSL certificate. This can also be specified via the VAULT_CAPATH environment variable
-client-cert <string>Path on the local disk to a single PEM-encoded CA certificate to use for TLS authentication to the Vault server. If this flag is specified, -client-key is also required. This can also be specified via the VAULT_CLIENT_CERT environment variable
-client-key <string>Path on the local disk to a single PEM-encoded private key matching the client certificate from -client-cert. This can also be specified via the VAULT_CLIENT_KEY environment variable
-header-key <string>Key-value pair provided as key=value to provide http header added to any request done by the CLI.Trying to add headers starting with 'X-Vault-' is forbidden and will make the command fail This can be specified multiple times
-mfa <string>Supply MFA credentials as part of X-Vault-MFA header. This can also be specified via the VAULT_MFA environment variable
-namespace <string>The namespace to use for the command. Setting this is not necessary but allows using relative paths. -ns can be used as shortcut. The default is (not set). This can also be specified via the VAULT_NAMESPACE environment variable
-non-interactive <string>When set true, prevents asking the user for input via the terminal. The default is false
-output-curl-string <string>Instead of executing the request, print an equivalent cURL command string and exit. The default is false
-policy-override <string>Override a Sentinel policy that has a soft-mandatory enforcement_level specified The default is false
-tls-server-name <string>Name to use as the SNI host when connecting to the Vault server via TLS. This can also be specified via the VAULT_TLS_SERVER_NAME environment variable
-tls-skip-verify <string>Disable verification of TLS certificates. Using this option is highly discouraged as it decreases the security of data transmissions to and from the Vault server. The default is false. This can also be specified via the VAULT_SKIP_VERIFY environment variable
-unlock-key <string>Key to unlock a namespace API lock. The default is (not set)
-wrap-ttl <string>Wraps the response in a cubbyhole token with the requested TTL. The response is available via the 'vault unwrap' command. The TTL is specified as a numeric string with suffix like '30s' or '5m'. This can also be specified via the VAULT_WRAP_TTL environment variable
-format <string>Print the output in the given format. Valid formats are 'table', 'json', 'yaml', or 'pretty'. The default is table. This can also be specified via the VAULT_FORMAT environment variable
-cancelReset the root token generation progress. This will discard any submitted unseal keys or configuration. The default is false
-decode <string>The value to decode; setting this triggers a decode operation. If the value is '-' then read the encoded token from stdin
-dr-tokenSet this flag to do generate root operations on DR Operational tokens. The default is false
-generate-otpGenerate and print a high-entropy one-time-password (OTP) suitable for use with the '-init' flag. The default is false
-initStart a root token generation. This can only be done if there is not currently one in progress. The default is false
-nonce <string>Nonce value provided at initialization. The same nonce value must be provided with each unseal key
-otp <string>OTP code to use with '-decode' or '-init'
-pgp-key <string> <keybase:user>Path to a file on disk containing a binary or base64-encoded public PGP key. This can also be specified as a Keybase username using the format 'keybase:<username>'. When supplied, the generated root token will be encrypted and base64-encoded with the given public key
-recovery-tokenSet this flag to do generate root operations on Recovery Operational tokens. The default is false
-statusPrint the status of the current attempt without providing an unseal key. The default is false