Bug 2025858

Summary:	[RFE] Add a module to deploy custom SSL certificates on the Satellite and Capsule
Product:	Red Hat Satellite	Reporter:	dgupte
Component:	Ansible Collection	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.10.0	CC:	dsinglet, ehelms
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 01:06:17 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 dgupte 2021-11-23 08:35:10 UTC

1. Proposed title of this feature request
>>>> 
Add a module to deploy custom SSL certificates on the Satellite and Capsule servers

What is the nature and description of the request?  
>>>>
Currently, it is not possible to deploy custom SSL certificate on Satellite and Capsule through Ansible Collections and need to use manual approach to configure the same.

  https://console.redhat.com/ansible/automation-hub/repo/published/redhat/satellite

1) For Satellite:  https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/installing_satellite_server_from_a_connected_network/index#configuring-satellite-custom-server-certificate_satellite
 https://access.redhat.com/solutions/1273623

2) For Capsule:   https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/installing_capsule_server/index#deploying-a-custom-ssl-certificate-to-capsule-server_capsule

It will be easier if we can provide SSL certificates in the collection and it would do the rest of configuration part.

Comment 2 Brad Buckingham 2023-07-21 20:38:13 UTC

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation.

Comment 3 Eric Helms 2024-06-06 01:06:17 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 "SAT-" 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.