Fix OAEP config in CRSEnrollment #4430
Merged
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 EngineConfig.getUseOAEPKeyWrap() has been added to read the keyWrap.useOAEP param from CS.cfg. All code that reads this param has been modified to use this method.
Previously the CRSEnrollment was trying to get the keyWrap.useOAEP param from the authority config, but it's actually reading a non-existent ca.keyWrap.useOAEP param. To fix the problem the code has been modified to call the EngineConfig.getUseOAEPKeyWrap().
edewata
changed the title
|
Kudos, SonarCloud Quality Gate passed! |
jmagne
approved these changes
May 3, 2023
|
@jmagne 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
EngineConfig.getUseOAEPKeyWrap()has been added to read thekeyWrap.useOAEPparam fromCS.cfg. All code that reads this param has been modified to use this method.Previously the
CRSEnrollmentwas trying to get thekeyWrap.useOAEPparam from the authority config, but it's actually reading a non-existentca.keyWrap.useOAEPparam.To fix the problem the code has been modified to call the
EngineConfig.getUseOAEPKeyWrap()as well.