mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
* 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>
66 lines
2.2 KiB
Plaintext
66 lines
2.2 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: operator unseal - Command
|
|
description: |-
|
|
The "operator unseal" allows the user to provide a portion of the root key
|
|
to unseal a Vault server.
|
|
---
|
|
|
|
> [!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.
|
|
|
|
# operator unseal
|
|
|
|
The `operator unseal` allows the user to provide a portion of the root key to
|
|
unseal a Vault server. Vault starts in a sealed state. It cannot perform
|
|
operations until it is unsealed. This command accepts a portion of the master
|
|
key (an "unseal key").
|
|
|
|
The unseal key can be supplied as an argument to the command, but this is
|
|
not recommended as the unseal key will be available in your history:
|
|
|
|
```shell-session
|
|
$ vault operator unseal IXyR0OJnSFobekZMMCKCoVEpT7wI6l+USMzE3IcyDyo=
|
|
```
|
|
|
|
Instead, run the command with no arguments and it will prompt for the key:
|
|
|
|
```shell-session
|
|
$ vault operator unseal
|
|
Key (will be hidden): IXyR0OJnSFobekZMMCKCoVEpT7wI6l+USMzE3IcyDyo=
|
|
```
|
|
|
|
For more information on sealing and unsealing, please the [seal concepts
|
|
page](/vault/docs/concepts/seal).
|
|
|
|
## Examples
|
|
|
|
Provide an unseal key:
|
|
|
|
```shell-session
|
|
$ vault operator unseal
|
|
Key (will be hidden):
|
|
Sealed: false
|
|
Key Shares: 1
|
|
Key Threshold: 1
|
|
Unseal Progress: 0
|
|
```
|
|
|
|
## Usage
|
|
|
|
The following flags are available in addition to the [standard set of
|
|
flags](/vault/docs/commands) included on all commands.
|
|
|
|
### Output options
|
|
|
|
- `-format` `(string: "table")` - Print the output in the given format. Valid
|
|
formats are "table", "json", or "yaml". This can also be specified via the
|
|
`VAULT_FORMAT` environment variable.
|
|
|
|
### Command options
|
|
|
|
- `-migrate` `(bool: false)` - Indicate that this share is provided with the intent that it is part of a seal migration process.
|
|
|
|
- `-reset` `(bool: false)` - Discard any previously entered keys to the unseal
|
|
process.
|