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
Describe the bug
This issue builds on top of #153.
Every time we call the hash method of the PBKDF2 hashing function, the following message gets logged:
Global salt length is not defined in properties file. Default value is used (64). Please set property global.salt.length in your psw4j.properties file.
We would like to suppress/remove this logging message when running in environments that don't use the psw4j.properties file.
To Reproduce
Run password4j without supplying psw4j.properties file and call PBKDF2's hash method
Expected behavior
Ideally either completely suppress this message or not log it at WARN level when running in restricted environments
The text was updated successfully, but these errors were encountered:
HashBuilder#addRandomSalt() implies a configuration file.
Unfortunately, I haven't updated the wiki yet, which mentions that a 64 byte salt will be generated without referencing the configuration file (old behavior).
So every time you use Password.hash(...).addRandomSalt().... the library checks the in-memory version of the psw4j.properties file.
If you use instead HashBuilder#addRandomSalt(int) the configurations in the files are overridden.
Describe the bug
This issue builds on top of #153.
Every time we call the hash method of the PBKDF2 hashing function, the following message gets logged:
Global salt length is not defined in properties file. Default value is used (64). Please set property global.salt.length in your psw4j.properties file.
We would like to suppress/remove this logging message when running in environments that don't use the psw4j.properties file.
To Reproduce
Run password4j without supplying psw4j.properties file and call PBKDF2's hash method
Expected behavior
Ideally either completely suppress this message or not log it at WARN level when running in restricted environments
The text was updated successfully, but these errors were encountered: