You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
When using WinFoom on Linux I am using a JSON file for my settings. When I use "encode(....)" within that JSON file it is not being interpreted. The literal "encode(....)" ends up as the effective password, instead of the base64 decoded value within the "encode()" tag.
To Reproduce
Steps to reproduce the behavior:
Just make a JSON setting file with the encode() tag for the password.
Expected behavior
I would expect that the System init would decode the provided value, just like with using a properties file
The text was updated successfully, but these errors were encountered:
This is not an issue. The encoding/decoding only take place when a confidential value is serialized/de-serialized into/from a system properties file. It wasn't designed for JSON input files.
Bug description
When using WinFoom on Linux I am using a JSON file for my settings. When I use "encode(....)" within that JSON file it is not being interpreted. The literal "encode(....)" ends up as the effective password, instead of the base64 decoded value within the "encode()" tag.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect that the System init would decode the provided value, just like with using a properties file
The text was updated successfully, but these errors were encountered: