Enable changing the provider for X509 certificate #2795
Merged
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.
Description
The provider used for issuing X509 certificates is currently fixed to BC. We have added a new property to allow changing this provider. Depending on the provider used, the RSAPrivateCrtKey interface might not be implemented. In such cases, casting will fail and an error will occur. Therefore, as a workaround, we have added the ATHENZ_CRYPTO_AUTHORITY_KEY_IDENTIFIER property to allow selecting whether to add the AUTHORITY KEY IDENTIFIER as an extension.
athenz/libs/java/auth_core/src/main/java/com/yahoo/athenz/auth/util/Crypto.java
Line 742 in 4d18d62
Contribution Checklist:
Attach Screenshots (Optional)