Sachini De Silva
Sachini De Silva
Above reported issue was fixed by adding [1]. But it leads to below issue due to confusing use of the system property preserveCaseSensitive. This needs to be fixed. Scenario: We...
This was due to incorrect equals sign('= =') in the sample policy. After correcting this I was able to create the policy without any errors.
This issue is not reproducible in latest APIM pack, hence closing.
This issue is already reported against cipher-tool at https://github.com/wso2/cipher-tool/issues/60. As a workaround for the moment, we can add the [secret] config at the bottom of the deployment.toml