Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Bug 2061773

Summary:	Settings defined by DSL are not properly encrypted
Product:	Red Hat Satellite	Reporter:	Ondřej Ezr <oezr>
Component:	Security	Assignee:	Ondřej Ezr <oezr>
Status:	CLOSED ERRATA	QA Contact:	Shweta Singh <shwsingh>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	ehelms, lzap, mhulan, pcreech, shwsingh
Target Milestone:	6.11.0	Keywords:	Triaged
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:	2022-07-05 14:34:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Ondřej Ezr 2022-03-08 14:24:55 UTC

Created from redmine issue https://projects.theforeman.org/issues/34573

Comment 2 Ondřej Ezr 2022-03-08 14:24:56 UTC

Upstream bug assigned to oezr

Comment 3 Bryan Kearney 2022-03-09 16:05:42 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34573 has been resolved.

Comment 5 Shweta Singh 2022-04-26 07:12:54 UTC

FailedQA

This issue can be reproduced on snap17 as fixed foreman version is not available on RHEL7 or RHEL8.

Expected output:
Value of setting should be encrypted.

Actual Output:
Setting value is not encrypted.

Comment 9 Shweta Singh 2022-05-16 07:52:11 UTC

Thanks Marek for debugging this issue. It looks like there is an issue while provisioning which creates an empty encryption file. 

Verified on Sat 6.11 Snap 20. 
This BZ is fixed but we need to fix the satellite provisioning which creates empty encryption file.
The testing steps shared by Dev in first comment works and "root password" is encrypted(Provided encryption key is present).

Comment 12 errata-xmlrpc 2022-07-05 14:34:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498