Bug #22694

[RFE] katello-certs-check to distinguish between Satellite and Capsule

Added by Chris Roberts over 4 years ago. Updated about 4 years ago.

Target version:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


Description of problem:
Currently, katello-certs-check checks provided certs and suggest their usage by running katello-installer and/or capsule-certs-generate. Following the output, one can be confused where to use the certificates and there have been attempts to use Satellite's certs for Capsule.

Please remove this ambiguity by printing just katello-installer XOR capsule-certs-generate. It should be enough to compare "CN" part of Subject in the server cert with FQDN of the machine running the script. If those matches, it is assumed the certs are meant for the Satellite and just "katello-installer" part of output shall be printed. If FQDN doesn't match CN of Subject, print just "capsule-certs-generate" part.

(the above is based on assumption that CN of a server's certificate must match the server's FQDN - not sure if this is correct)

Ideally, there should be a line "Provided server's certificate was recognized as a cert for Satellite/Capsule", just to clarify to user the decision the script did.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Have some custom certs and run

Actual results:
Currently it is ambiguous if I should run katello-installer or capsule-certs-generate.

Expected results:
The tool shall print our either katello-installer example XOR capsule-certs-generate example, not both.

Associated revisions

Revision e521bbab (diff)
Added by Chris Roberts over 4 years ago

Fixes #22694 - added check on cert hostname output


#1 Updated by Chris Roberts over 4 years ago

  • Legacy Backlogs Release (now unused) set to 338

#2 Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request added

#3 Updated by Chris Roberts over 4 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF