Bug 1006419

Summary:	Improve handling of obfuscated passwords for installation
Product:	[Other] RHQ Project	Reporter:	Jay Shaughnessy <jshaughn>
Component:	Installer	Assignee:	Jay Shaughnessy <jshaughn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	asantos, hrupp
Target Milestone:	ER02
Target Release:	RHQ 4.10
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-23 12:30:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	996779
Bug Blocks:	1006862

Description Jay Shaughnessy 2013-09-10 15:08:39 UTC

There are three rhq-server.properties requiring obfuscated passwords:
  rhq.storage.password
  rhq.server.database.password
  rhq.server.management.password

The values for these properties must currently be generated by executing:

  rhq-installer.sh|bat --encodepassword <plainTextPassword>


There are two problems with this:

1) The <plainTextPassword> should be prompted for as opposed to being a
   supplied on the command line.

   Currently the PTP will be held in command prompt history.

2) Running this utility is not always convenient, and should be optional.

   If the obfuscated password values are not set in rhq-server.properties
   then they should be prompted for by the installer.  This will allow
   several ways for the user to proceed with install.

Note that we must always allow for silent installation.

Comment 9 Heiko W. Rupp 2014-04-23 12:30:16 UTC

Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.