use p12 for signing certificate #300
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
ubhaller
force-pushed
the
feature/crypto-provider-uses-p12
branch
from
0f51a09 to
4e9c4ad
Compare
martinalig
force-pushed
the
feature/crypto-provider-uses-p12
branch
from
6afacbd to
5ae34ea
Compare
|
Kudos, SonarCloud Quality Gate passed! |
martinalig
approved these changes
Apr 21, 2021
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.
Change the
CryptoProviderto use a base64 encoded P12 and a corresponding password to load the signing certificate and signing private key. This unifies theEfgsGatewayConfigso that both key pairs use a p12 container to store private and public material.Also missing tests for the
CryptoProviderwere added.