Bug 1973374 - [RFE] Add feature in "katello-certs-check" to check for an unsupported character in the hostname
Summary: [RFE] Add feature in "katello-certs-check" to check for an unsupported charac...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Certificates
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-17 17:19 UTC by Ganesh Payelkar
Modified: 2023-03-13 13:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ganesh Payelkar 2021-06-17 17:19:55 UTC
Description of problem:

Add feature in "katello-certs-check" to check for an unsupported character in the hostname 

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

How reproducible:


Steps to Reproduce:
1. add the hostname with an underscore for capsule or satellite 
2. Installer will fail 
3.

Actual results:

 `# capsule-certs-generate [...] --foreman-proxy-cname "sat_cap3.lb.example.com"`

 `Parameter foreman-proxy-cname invalid: Elements of the array are invalid: sat_cap3.lb.example.com must match one of (?-mix:\A(([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\-]*[A-Za-z0-9])\z) during configuration, exiting`

Expected results: 

If we can check the SSL certs or the SAN has such hostname, we can warn customers that those hostnames are not supported. 


Additional info:

Comment 6 Brad Buckingham 2023-01-04 22:48:23 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


Note You need to log in before you can comment on or make changes to this bug.