Add HSM support for LWCA #4659
Merged
Add HSM support for LWCA #4659
Conversation
This file contains 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
The CAEngine.createCA() has been modified to get the token name from LWCA's keyNickname. If the token name exists, it will use that token to create the private key and store the cert. Otherwise, it will use the internal token. The CASigningUnit.init() has been modified to get the token name from name from LWCA's keyNickname. If the token name exists, it will use that token to load the cert and the private key, and for signing and verification. Otherwise, it will use the internal token. The LWCA test with HSM has been modified to verify that the LWCA cert and key will be created in HSM instead of internal token. Resolves: dogtagpki#2412
|
|
@fmarco76 Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
CAEngine.createCA()has been modified to get the token name from LWCA'skeyNickname. If the token name exists, it will use that token to create the private key and store the cert. Otherwise, it will use the internal token.The
CASigningUnit.init()has been modified to get the token name from name from LWCA'skeyNickname. If the token name exists, it will use that token to load the cert and the private key, and for signing and verification. Otherwise, it will use the internal token.The LWCA test with HSM has been modified to verify that the LWCA cert and key will be created in HSM instead of internal token.
Resolves: #2412