Bug 2185634

Summary:	[RFE] Provide an alternate method of katello-ca-cosumer to populate custom SSL certs on client systems
Product:	Red Hat Satellite	Reporter:	Sayan Das <saydas>
Component:	Registration	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.12.3	CC:	ahumbe, dhjoshi, lstejska, mveiga, wpinheir
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:12:46 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 Sayan Das 2023-04-10 17:03:39 UTC

1. Proposed title of this feature request

A similar option like curl command from Global Registration method, to update\refresh SSL certs on the client systems connected with satellite\capsule instead of using katello-ca-consumer rpm

2. What is the nature and description of the request?

Introduction of a snippet\template which can be used to generate a curl command and use the same to update\refresh SSL certs on the client systems

3. Why does the customer need this? (List the business requirements here)

This RFE is an extension of https://bugzilla.redhat.com/show_bug.cgi?id=2124052 basically.

Since katello-ca-consumer rpm has been deprecated and no longer being used for registration purposes, If SSL CA changes in satellite, Then end-users have only one option left with them i.e. completely re-register the system.

But It should not be required. We should have a similar option present to generate a curl command, that will help deploying the new SSL CA on the client systems.

4. How would the customer like to achieve this? (List the functional requirements here)

In the same was as we generate and use the curl command for Global Registration method

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

* Install satellite

* Register a client system

* Install custom SSL certs on satellite

* Use the new feature to update the CA on the client system

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

7. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

Satellite 6.13 or as soon as it's feasible

8. Is the sales team involved in this request and do they have any additional input?

9. List any affected packages or components.

foreman

10. Would the customer be able to assist in testing this functionality if implemented?

RH support can

Comment 1 Sayan Das 2023-06-26 16:07:35 UTC

Can we recommend this as an alternative to installing katello-ca-consumer, for every client system, after a SSL CA renewal ?

# _SERVER=$(subscription-manager config | awk '/ hostname/{print $NF}'| tr -d '[]')

# curl http://$_SERVER/pub/katello-rhsm-consumer | bash

# subscription-manager refresh



-- Sayan

Comment 2 Marek Hulan 2024-02-14 13:46:08 UTC

Sayan, this file relies on katello-ca-consumer package, once that's dropped, this file will no longer exist.

Comment 3 Sayan Das 2024-02-14 13:59:34 UTC

I do understand that. When i had proposed those steps, https://projects.theforeman.org/issues/36747 was not yet fixed.

But with https://projects.theforeman.org/issues/36747 fixed and a new subscription_manager_setup snippet developed, I think some UI option can be created to make use of this snippet to fix RHSM config or update the CA certs as needed, on client systems.

Comment 4 Eric Helms 2024-06-06 16:12:46 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.