Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Passwords should not be saved in cleartext. When you run katello-installer, it saves the cleartext password.

Not only that, every time you run katello-installer successfully after that it gets echoed back. 

Really bad practice.

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

How reproducible:
Always

Steps to Reproduce:
1. katello-installer --foreman-admin-password=redhat
2. katello-installer --capsule-tftp=true
3. Look at your password being displayed.

Actual results:
You see the password printed in clear text.

Expected results:
The same output, but without the password.


Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Is this actually rel note material?
What sort of doc text would be suitable?

thanks

Reset docs contact <> daobrien

Chris, do note the echoing back on subsequent runs is solved already in BZ1125414.  

My personal opinion is WONTFIX on saving in clear text, due to the nature of the installer it'd be quite complicated to avoid this.  Change the password from the default after installation is the only way to avoid the saved password being the correct one. The installer saves a variety of other confidential info too like oauth tokens which are just as useful as the admin password, but all this stuff is only readable by the root user.

Stephen,

I agree lets close this one out since the subsequent runs is already solved. 

Moving to wontfix based on your suggestions.