-
Notifications
You must be signed in to change notification settings - Fork 11
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
encode() not working for a JSON settings file #8
Comments
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. |
Ok, I did not know that. Thanks for pointing that out. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: