-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
getting a NULL pointer exception when encrypting passwords in deployement.toml file #60
Comments
@shagihan , Thanks |
Adding a new line after the [secrets] section solved the issue. Eg.
|
This issue still persists in AM-3.0.0. Steps to reproduce This can be reproduced when the [secrets] section defined between the other defined configs in the deployment.toml file. With the NPE, the deployment.toml file will get corrupted and all the configurations below the [secrets] section will get lost. If the [secrets] section is defined at the end of the deployment.toml file, this issue is not occurring. |
We are still observing the same error. There is a workaround for this issue to place the secure vault block at the end of the file, but the issue needs to be properly fixed.
|
This issue is available in APIM 3.1.0 too and the document[1] did not mention putting this as last(as a workaround) to resolve this issue. |
The issue happens because, cipher-tool/components/ciphertool/src/main/java/org/wso2/ciphertool/CipherTool.java Lines 378 to 389 in 89c0cf1
This block is only intended to process the cipher-tool/components/ciphertool/src/main/java/org/wso2/ciphertool/CipherTool.java Line 386 in 89c0cf1
Therefore, introducing an isNotProcessed variable to the code and not passing subsequent configuration blocks through this if block will avoid the NPE.
|
Description:
Getting the following exception when running cipher tool for the first time with the -Dconfigure parameter
Suggested Labels:
cipher-tool,toml
Steps to reproduce:
The text was updated successfully, but these errors were encountered: