This repository has been archived by the owner on Jan 21, 2024. It is now read-only.
Encrypted Private Key Fix #7
Open
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
Fixed error when signing JWT with encrypted private key. Error: Unable to create OpenSSL PBDKF: PBKDF-OpenSSL SecretKeyFactory not available
cajhughes
added a commit
to mulesoft-catalyst/jwt-module
that referenced
this pull request
Jan 5, 2024
Incorporate pull request, and upgrade dependencies mulesoft-consulting#7
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When we were trying to sign JWT with encrypted private keys, we were getting error: Unable to create OpenSSL PBDKF: PBKDF-OpenSSL SecretKeyFactory not available.
To fix this error added the BouncyCastleProvider in JwtOperations class. Now we are able to sign JWT using encrypted private keys.