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):
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 ***