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 2096313

Summary: The text info in bmc > password is not accurate
Product: Red Hat Satellite Reporter: Kobi Hakimi <khakimi>
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.1CC: apatel, aruzicka, inecas, kgaikwad
Target Milestone: UnspecifiedKeywords: 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: 2023-08-10 07:48:38 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:
Attachments:
Description Flags
bmc password info snapshot none

Description Kobi Hakimi 2022-06-13 13:59:58 UTC 
Created attachment 1889421 [details]
bmc password info snapshot

Description of problem:
The text info in bmc > password is not accurate 

Version-Release number of selected component (if applicable):
Red Hat Satellite (build: 6.10.1.1)
Version 6.10 © 2022 Red Hat Inc.


How reproducible:
100%

Steps to Reproduce:
1. Open the host for edit 
2. Go to the Interfaces tab
3. Open for Edit the BMC interface
4. Hover with the mouse next to the "i" (info) of the Password field


Actual results:
You will see the following message(see attached snapshot):
"""
The BMC password will be used by Satellite to access the host's BMC controller via a BMC-enabled capsule, if available.
The password will also be accessible to other users via templates and in the ENC YAML output; disable the bmc_credentials_accessible setting to prevent access.
"""

Expected results:
The password will NOT be accessible to other users via templates and in the ENC YAML output.
since we had the following CVE:
https://github.com/advisories/GHSA-7h9m-xcfj-p257

Additional info:
Thanks to orabin for her help on this issue
Comment 2 Brad Buckingham 2023-07-21 21:06:39 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 3 Kobi Hakimi 2023-07-24 15:26:33 UTC 
Hi,
I looked at our Satellite instance and I can see that the text info is already fixed with the following text:
The BMC password will be used by Satellite to access the host's BMC controller via a BMC-enabled capsule, if available.
The password will not be accessible to other users; enable the bmc_credentials_accessible setting to permit access via templates and in the ENC YAML output.

IMHO you can close it as duplicate or fixed.

Thanks,
   Kobi
Comment 4 Adam Ruzicka 2023-08-10 07:48:38 UTC 
Closing per #3 as fixed in current release. If you feel there is still something that should be addressed here, feel free to reopen.