Bug 1576052

Summary:	[RFE] Encrypt password in ~/.hammer/cli.modules.d/foreman.yml
Product:	Red Hat Satellite	Reporter:	Skip Wyatt <awyatt>
Component:	Hammer	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Suraj Bora <sbora>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3.1	CC:	akarsale, apatel, bkearney, dhlavacd, gapatil, kgaikwad, mhulan, rabajaj, sami.kessavdjeedjouma, suarora, tstrachota
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-12-06 18:22:48 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:

Description Skip Wyatt 2018-05-08 16:22:32 UTC

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.

Comment 1 Skip Wyatt 2018-05-08 16:24:05 UTC

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

This should read hammer auth

Comment 4 Marek Hulan 2018-09-14 08:24:17 UTC

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.

Comment 5 Bryan Kearney 2018-12-06 18:22:48 UTC

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