Bug 2070341

Summary:	Support for non-password fencing authentication for HP ILO and VMware
Product:	Red Hat Enterprise Linux 8	Reporter:	Tom Sorensen <tsorense>
Component:	fence-agents	Assignee:	Oyvind Albrigtsen <oalbrigt>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.5	CC:	arahmad, cfeist, cluster-maint, sbradley
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---
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-09-22 19:38:22 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 Tom Sorensen 2022-03-30 21:06:54 UTC

Description of problem:
Support for non-password authentication in HP ILO and VMware fence agents.


Additional info:
Both HP ILO and VMware REST support use of certificates for authentication. Currently fence-agents do not (except ssh, which allows for keys).

RFE for supporting certificates, OATH, tokens, keys, etc. as appropriate for both HP ILO and VMware.

HP ILO v2+ appear to support (v5 docs -- http://itdoc.hitachi.co.jp/manuals/ha8000v/hard/Gen10/iLO/880740-004_en.pdf)

VMware REST supports (https://developer.vmware.com/apis/vsphere-automation/latest/vcenter/#/)

Unclear that VMware SOAP supports; initial indication is that it does not.

Allowing for non-password authn would allow for customers to improve security and more easily change authn information.

Comment 9 RHEL Program Management 2023-09-22 19:35:46 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 10 RHEL Program Management 2023-09-22 19:38:22 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.