Use protection level HSM if it's given in the URI#809
Merged
Conversation
This commit prioritizes the `hsm=true` flag in the URI to create a key in an Azure HSM Key Vault. Before this change, `step-kms-plugin` required the use of the flag `--protection-level HSM` to create a key in the HSM. Fixes smallstep/step-kms-plugin#252
hslatman
approved these changes
Jul 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit prioritizes the
hsm=trueflag in the URI to create a key in an Azure HSM Key Vault. Before this change,step-kms-pluginrequired the use of the flag--protection-level HSMto create a key in the HSM.Fixes smallstep/step-kms-plugin#252