Bug 870516 - Key store passwords are not loaded from rhq-server.properties file in RHQ advanced configuration installer page
Key store passwords are not loaded from rhq-server.properties file in RHQ adv...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Installer (Show other bugs)
All All
unspecified Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-10-26 13:50 EDT by Larry O'Leary
Modified: 2012-10-26 13:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
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:


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

How reproducible:

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.

Note You need to log in before you can comment on or make changes to this bug.