Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow pre-resolved seeds #436

Merged
merged 4 commits into from
Nov 19, 2024
Merged

Allow pre-resolved seeds #436

merged 4 commits into from
Nov 19, 2024

Conversation

peterbroadhurst
Copy link
Contributor

Currently the config-time loading of seed key materials, only supports key stores where the resolution of a name/path/index is a fully-deterministic loading instruction for a key material.

However, there are cases where the result of this must be stored back to the DB in key manager when resolving keys. Particularly when using "master key encryption" approaches, where the keyHandle will be an encrypted representation of a key that can only be decrypted by the HSM.

This PR proposes the keyHandle can be supplied directly in the configuration for seed loading, mimicking the post-resolution state - where the keyHandle has been persisted. This allows the configuration to:

  • Bypass FindOrCreateLoadableKey
  • Jump straight to LoadKeyMaterial

Copy link
Contributor

@dwertent dwertent left a comment

Choose a reason for hiding this comment

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

LGTM

@dwertent dwertent merged commit dc3f1b8 into main Nov 19, 2024
6 checks passed
@dwertent dwertent deleted the seed-keyhandle branch November 19, 2024 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants