Open
Conversation
…error messages and improve file reading logic
…d maintain JKS compatibility
Contributor
|
Generate the doc changes by running |
npamudika
reviewed
Aug 13, 2025
npamudika
reviewed
Aug 13, 2025
npamudika
reviewed
Aug 13, 2025
npamudika
reviewed
Aug 13, 2025
npamudika
reviewed
Aug 13, 2025
npamudika
reviewed
Aug 13, 2025
This file contains hidden or 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
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.
Purpose
Currently, we only support JKS keystores in
apiclt secretcommands. However, we identified an issue where, in the 4.4.0 and 4.5.0 packs, the default bundle keystore is PKCS12. As a result, if someone tries to usewso2carbon.jksto encrypt secrets, the operation will fail.Goals
To resolve this issue, we need to update
apictlto support both JKS and PKCS12 keystores.Approach