Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.5, 2.2
-
None
-
Security Level: public (Regular issues)
-
None
Description
keystorePass does not conform to the current convention for encrypting/obscuring GBean attributes. Currently, attribute names with 'password' will be encrypted.
We should either recognize keystorePass as an attribute requiring encryption or add a new keystorePassword attribute and start using that (with some appropriate migration logic, if a 'keystorePass' is configured). I guess I prefer the latter option. Other opinions?