[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1816) Suckerpassward not properly handled in ServerPeer.startService(), making a restart fail.

[Howard Gao (JIRA)]

     [ https://jira.jboss.org/browse/JBMESSAGING-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard Gao closed JBMESSAGING-1816.
-----------------------------------



> Suckerpassward not properly handled in ServerPeer.startService(), making a restart fail.
> ----------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1816
>                 URL: https://jira.jboss.org/browse/JBMESSAGING-1816
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: AS Integration
>    Affects Versions: 1.4.7.GA
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>             Fix For: 1.4.0.SP3.CP11, 1.4.8.GA
>
>
> The suckerpassword is not handled properly in ServerPeer.startService():
>          if (suckerPassword == null)
>       	{
>          	suckerPassword = SecurityMetadataStore.DEFAULT_SUCKER_USER_PASSWORD;
>       	}
>          else
>          {
>             //https://jira.jboss.org/jira/browse/JBMESSAGING-1806
>             suckerPassword = new String(SecurityUtil.decode(suckerPassword));
>          }
> When the server peer is stopped and restarted (not shutdown the whole process), it will result in decoding a plain password (instead of an encrypted password).
> Consider to move it to the setSuckerPassword().

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira