“Our RHEL satellite uses the old RHN method.”
We worked with a consultant who confirmed that if we follow the steps below, we can still leverage BigFix to patch RHEL:
- Create the necessary file path on the root BigFix server for the RHSM SSL certificate as per the documentation and install.
- Enable and subscribe applicable Linux patching sites (CentOS 6/7 and/or RHEL 6/7).
- Setup the RHSM v2 download plugin on the root BigFix server via the BES console dashboard as a master operator as per the documentation.
- Configure any applicable custom repositories as per the documentation.
- Update DownloadWhitelist on root BigFix server with applicable repository URLs, etc.
- Deploy applicable content to enable custom repositories for specific endpoints.
But I am not authorized to “create and download identification certificates through the Red Hat Subscription Management system to use the RHSM Download Plug-in”. There is a person in my organization that can do this, but they are not responding to my request because the term RHSM is foreign to them because “…our RHEL satellite uses the old RHN method.”
What is an RHSM SSL Certificate?
My educated guess (from what i understood from the two links down below) is that an “RHSM SSL Certificate” is an identity certificate which comprises of an entitlement certificate and an identify certificate. Both must be created and downloaded through the Red Hat Subscription Management system.
And I gathered that we “…must register the RHSM download plug-in to avoid download errors” and that “Registration is required though the data that the download plug-in generates will not be used.” And this is an important to note because “…our RHEL satellite uses the old RHN method”.
Could someone please confirm or correct my answer.