Skip to content

Conversation

@dmihalcik-virtru
Copy link
Member

Proposed Changes

Checklist

  • I have added or updated unit tests
  • I have added or updated integration tests (if appropriate)
  • I have added or updated documentation

Testing Instructions

- Looking up a key now loads the `manager` field in the key provider
- This is required, as the manager should be the factory key, not the name
- This allows us to load the same manager multiple times with different configs.

HOWEVER the config is only looked at on the first load; we should update this so it evicts and reloads the provider if the config changes. This will come in a follow-up.
Example HSM plugin using Hashicorp Vault as a key provider
@github-actions github-actions bot added comp:db DB component comp:policy Policy Configuration ( attributes, subject mappings, resource mappings, kas registry) comp:ci Github Actions Work comp:kas Key Access Server comp:examples comp:lib:ocrypto size/xl labels Oct 28, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 28, 2025

Dependency Review

The following issues were found:

  • ❌ 1 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 14 package(s) with unknown licenses.

View full job summary

- uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
with:
persist-credentials: false
- uses: actions/setup-go@d35c59abb061a4a6fb18e82ac0862c26744d6ab5 # v5.5.0

Check failure

Code scanning / zizmor

runtime artifacts potentially vulnerable to a cache poisoning attack Error

runtime artifacts potentially vulnerable to a cache poisoning attack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp:ci Github Actions Work comp:db DB component comp:examples comp:kas Key Access Server comp:lib:ocrypto comp:policy Policy Configuration ( attributes, subject mappings, resource mappings, kas registry) size/xl

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants