[
https://issues.apache.org/jira/browse/GERONIMO-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773508#action_12773508
]
Ashish Jain commented on GERONIMO-4927:
---------------------------------------
IMO the best way without introducing much complexity would be to have a line of
code checking for keystorePass attribute. In this way we may not have to worry
about migration issues. I have generated a patch. Please verify. Thanks.
> keystorePass attribute on TomcatWebSSLConnector GBean should be
> encrypted/obscured
> ----------------------------------------------------------------------------------
>
> Key: GERONIMO-4927
> URL: https://issues.apache.org/jira/browse/GERONIMO-4927
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.1.5, 2.2
> Reporter: Kevan Miller
> Fix For: 2.1.5, 2.2.1, 3.0
>
>
> 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?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
