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:

Customer performs automation using hammer and cannot have non-encrypted passwords at rest in ~/.hammer/cli.modules.d/foreman.yml

Because these are automated jobs, they do not have user interaction for foreman auth

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

Satellite 6.3.1

How reproducible:

Everytime

Expected results:
Customer wants an option like virt-who-password, which encrypts the password and performs a lookup based upon the hash for the user.

> Because these are automated jobs, they do not have user interaction for foreman auth

This should read hammer auth

Isn't the file owned by root already? the key benefit for virt-who-password is that only root can use it and the master password is still stored on harddrive in plaintext, just in other file accessible by root only. IMHO there's no point in adding this to hammer. Hammer now supports sessions and x509 certs (6.4 for x509 IIRC) so if people don't want to store password, they don't have to.

Also the very same request was closed in BZ 230204 as won't fix. I'd suggest closing this as a duplicate of the very same BZ.

As Marek mentioned, this has already been closed. Since we need the password in clear text we would need to symmetricly encrypt this password with another password that will need to be in clear text. Closing this out.

*** This bug has been marked as a duplicate of bug 230204 ***