open-vault/website/content/api-docs/system/generate-root.mdx
Jeff Escalante ec620a7765
Implement MDX Remote (#10581)
* implement mdx remote

* fix an unfenced code block

* fix partials path

Co-authored-by: Jim Kalafut <jkalafut@hashicorp.com>
2020-12-17 16:53:33 -05:00

168 lines
4.1 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
layout: api
page_title: /sys/generate-root - HTTP API
sidebar_title: <code>/sys/generate-root</code>
description: |-
The `/sys/generate-root/` endpoints are used to create a new root key for
Vault.
---
# `/sys/generate-root`
The `/sys/generate-root` endpoint is used to create a new root key for Vault.
## Read Root Generation Progress
This endpoint reads the configuration and process of the current root generation
attempt.
| Method | Path |
| :----- | :--------------------------- |
| `GET` | `/sys/generate-root/attempt` |
### Sample Request
```shell-session
$ curl \
http://127.0.0.1:8200/v1/sys/generate-root/attempt
```
### Sample Response
```json
{
"started": true,
"nonce": "2dbd10f1-8528-6246-09e7-82b25b8aba63",
"progress": 1,
"required": 3,
"encoded_token": "",
"pgp_fingerprint": "",
"otp_length": 24,
"complete": false
}
```
If a root generation is started, `progress` is how many unseal keys have been
provided for this generation attempt, where `required` must be reached to
complete. The `nonce` for the current attempt and whether the attempt is
complete is also displayed.
If a PGP key is being used to encrypt the final root
token, its fingerprint will be returned.
If an OTP is being used to encode the final root token it will be returned only
once, on the response to the start request.
The OTP is a base62 string, with length of otp_length.
The raw bytes (char codes) of the token will be XOR'd with
this value before being returned as a response to the final unseal
key, encoded as base64.
## Start Root Token Generation
This endpoint initializes a new root generation attempt. Only a single root
generation attempt can take place at a time.
| Method | Path |
| :----- | :--------------------------- |
| `PUT` | `/sys/generate-root/attempt` |
### Parameters
- `pgp_key` `(string: <optional>)` Specifies a base64-encoded PGP public key.
The raw bytes of the token will be encrypted with this value before being
returned to the final unseal key provider.
### Sample Request
```shell-session
$ curl \
--request PUT \
http://127.0.0.1:8200/v1/sys/generate-root/attempt
```
### Sample Response
```json
{
"started": true,
"nonce": "2dbd10f1-8528-6246-09e7-82b25b8aba63",
"progress": 1,
"required": 3,
"encoded_token": "",
"otp": "2vPFYG8gUSW9npwzyvxXMug0",
"otp_length": 24,
"complete": false
}
```
## Cancel Root Generation
This endpoint cancels any in-progress root generation attempt. This clears any
progress made. This must be called to change the OTP or PGP key being used.
| Method | Path |
| :------- | :--------------------------- |
| `DELETE` | `/sys/generate-root/attempt` |
### Sample Request
```shell-session
$ curl \
--request DELETE \
http://127.0.0.1:8200/v1/sys/generate-root/attempt
```
## Provide Key Share to Generate Root
This endpoint is used to enter a single master key share to progress the root
generation attempt. If the threshold number of master key shares is reached,
Vault will complete the root generation and issue the new token. Otherwise,
this API must be called multiple times until that threshold is met. The attempt
nonce must be provided with each call.
| Method | Path |
| :----- | :-------------------------- |
| `PUT` | `/sys/generate-root/update` |
### Parameters
- `key` `(string: <required>)` Specifies a single master key share.
- `nonce` `(string: <required>)`  Specifies the nonce of the attempt.
### Sample Payload
```json
{
"key": "acbd1234",
"nonce": "ad235"
}
```
### Sample Request
```shell-session
$ curl \
--request PUT \
--data @payload.json \
http://127.0.0.1:8200/v1/sys/generate-root/update
```
### Sample Response
This returns a JSON-encoded object indicating the attempt nonce, and completion
status, and the encoded root token, if the attempt is complete.
```json
{
"started": true,
"nonce": "2dbd10f1-8528-6246-09e7-82b25b8aba63",
"progress": 3,
"required": 3,
"pgp_fingerprint": "",
"complete": true,
"encoded_token": "FPzkNBvwNDeFh4SmGA8c+w=="
}
```