Bug 870516

Summary: Key store passwords are not loaded from rhq-server.properties file in RHQ advanced configuration installer page
Product: [Other] RHQ Project Reporter: Larry O'Leary <loleary>
Component: InstallerAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Larry O'Leary 2012-10-26 13:50:40 EDT
Description of problem:
When installing server with SSL enabled, the keystore and trusstore passwords are not loaded from rhq-server.properties and are instead left blank.

This affects the following configuration properties and their respective input field in the installer:

    rhq.communications.connector.security.keystore.password
    rhq.communications.connector.security.keystore.key-password
    rhq.communications.connector.security.truststore.password
    rhq.server.client.security.keystore.password
    rhq.server.client.security.keystore.key-password
    rhq.server.client.security.truststore.password

Version-Release number of selected component (if applicable):
4.4.0

How reproducible:
Always

Steps to Reproduce:
1. Run RHQ installer
2. Click on the link that says *Advanced* at the top of the page
3. Notice that the keystore and truststore passwords are empty
  
Actual results:
If sslsocket is used, the server fails to start due to an invalid keystore password being used with the default keystore.

Expected results:
Passwords should be present or at least loaded from rhq-server.properties during installation so the server properly starts when sslsocket is used.

Additional info:
This appears to be very similar to the issue that affects the database password at the top of the install page. Any field of type password seems to be affected. This does not affect the tomcat/servlet password properties because these fields appear to be plain text fields.