Skip to content

Conversation

rculpepper
Copy link
Contributor

No description provided.

@rculpepper rculpepper requested a review from a team as a code owner August 20, 2025 17:00
Copy link

github-actions bot commented Aug 20, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Wed Aug 20 17:23:10 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Wed Aug 20 17:17:36 UTC 2025

Copy link

Broken Link Checker

Full Github Actions output

@yhyakuna yhyakuna added the Vault Content update for Vault product docs label Aug 21, 2025
Comment on lines +1206 to +1211
This endpoint generates new keys derived from the named key's HMAC key and
encrypted using the named key. Optionally return the plaintext of the key as well.
Whether plaintext is returned depends on the path; as a result, you can use Vault
ACL policies to control whether a user is allowed to retrieve the plaintext value
of a key. This is useful if you want an untrusted user or operation to generate keys
that are then made available to trusted users.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This endpoint generates new keys derived from the named key's HMAC key and
encrypted using the named key. Optionally return the plaintext of the key as well.
Whether plaintext is returned depends on the path; as a result, you can use Vault
ACL policies to control whether a user is allowed to retrieve the plaintext value
of a key. This is useful if you want an untrusted user or operation to generate keys
that are then made available to trusted users.
The derived keys endpoint generates new keys based on the HMAC key associated
with the provided key name. Vault always returns keys encrypted with the
provided named and optionally returns the associated plaintext.
You can use Vault ACL policies to control which users can retrieve the plaintext
value of the keys. For example, to allow untrusted users or operations to
generate keys that are then available to trusted users.

Style correction: avoid "this" as a pronoun, avoid possessives, use complete sentences in paragraphs

| :----- | :----------------------------- |
| `POST` | `/transit/derivedkeys/:type/:name` |

### Parameters
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Parameters
### Path parameters

Comment on lines +1219 to +1222
- `type` `(string: <required>)` – Specifies the type of key to generate. If
`plaintext`, the plaintext keys will be returned along with the ciphertexts. If
`wrapped`, only the ciphertext value will be returned. This is specified as
part of the URL.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `type` `(string: <required>)` – Specifies the type of key to generate. If
`plaintext`, the plaintext keys will be returned along with the ciphertexts. If
`wrapped`, only the ciphertext value will be returned. This is specified as
part of the URL.
- `type` `(enum: <required>)` – Specifies the type of keys to generate.
- `plaintext` - return the plaintext keys along with the ciphertexts
- `wrapped` - only return the ciphertext values.

part of the URL.

- `name` `(string: <required>)` – Specifies the name of the encryption key to
use to encrypt the keys. This is specified as part of the URL.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
use to encrypt the keys. This is specified as part of the URL.
use to encrypt the keys.


- `name` `(string: <required>)` – Specifies the name of the encryption key to
use to encrypt the keys. This is specified as part of the URL.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Request parameters

- `name` `(string: <required>)` – Specifies the name of the encryption key to
use to encrypt the keys. This is specified as part of the URL.

- `salt` `(string: <required>)` - The salt input to derivation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- `salt` `(string: <required>)` - The salt input to derivation
- `salt` `(string: <required>)` - The salt input used to derive the new keys.


- `salt` `(string: <required>)` - The salt input to derivation

- `key_index_from` `(int: <required>)` - The starting index for keys to return
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean exactly? Index of what? And does the index start at 0 or 1?

(I think I know what we're trying to say, but it's not really a complete thought, so I don't want to assume)

of the data key. Must be 0 (for latest) or a value greater than or equal to the
min_encryption_version configured on the key.

- `info` `(string: "")` – The info string input to derivation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What does this mean?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Vault Content update for Vault product docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants