Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1964037 - wrong generation of /etc/tomcat/cert-users.properties
Summary: wrong generation of /etc/tomcat/cert-users.properties
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: Eric Helms
QA Contact: Radek Mynar
URL:
Whiteboard:
Depends On:
Blocks: 1399395
TreeView+ depends on / blocked
 
Reported: 2021-05-24 15:03 UTC by Jan Jansky
Modified: 2023-10-04 14:40 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2131768 2184132 (view as bug list)
Environment:
Last Closed: 2023-05-03 13:20:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman puppet-katello pull 457 0 None open Calculate the client DN for Artemis, ignoring empty values 2022-09-29 11:37:23 UTC
Red Hat Issue Tracker SAT-14042 0 None None None 2022-11-25 00:31:23 UTC
Red Hat Knowledge Base (Solution) 5912181 0 None None None 2021-06-02 01:06:46 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:20:50 UTC

Description Jan Jansky 2021-05-24 15:03:44 UTC 
Description of problem: 

Due to different approach between certificate generations and /etc/tomcat/cert-users.properties generation is possible to get authentication errors in candlepin.

If any empty string is used in certs part of /etc/foreman-installer/scenarios.d/satellite-answers.yaml as below

---
certs:
  country: US
  state: ''                <<<<<<<<<
  city: Raleigh
  org: Katello
  org_unit: ''             <<<<<<<<

certificate is generated without ST and OU as below

# grep Subject /etc/pki/katello/certs/java-client.crt
        Subject: C=US, O=candlepin, CN=localhost

however /etc/tomcat/cert-users.properties is generate with empty OU and ST as below

# cat /etc/tomcat/cert-users.properties
katelloUser=CN=localhost, OU=, O=candlepin, ST=, C=US

due to this mismatch authentication errors appear in /var/log/candlepin/error.log as below

2021-05-24 17:00:54,608 [thread=Thread-16 (activemq-netty-threads)] [=, org=, csid=] WARN  org.apache.activemq.artemis.core.server - AMQ222216: Security problem while authenticating: AMQ229031: Unable to validate user from /127.0.0.1:54708. Username: null; SSL certificate subject DN: CN=localhost, O=candlepin, C=US
2021-05-24 17:00:54,609 [thread=Thread-16 (activemq-netty-threads)] [=, org=, csid=] WARN  org.apache.activemq.artemis.core.protocol.stomp - AMQ332069: Sent ERROR frame to STOMP client /127.0.0.1:54708: Security Error occurred: User name [null] or password is invalid


and hammer ping

# hammer ping
candlepin_events: 
    Status:          FAIL
    message:         Not running
    Server Response: Duration: 2ms


Version-Release number of selected component (if applicable):
At least since satellite-installer-6.8.0.11-1.el7sat.noarch

How reproducible: Always


Steps to Reproduce:
1. Update /etc/foreman-installer/scenarios.d/satellite-answers.yaml
2. Fill some empty strings in certs category as 'state'
3. # satellite-installer --certs-regenerate true --certs-update-all --certs-update-server --certs-update-server-ca

Actual results:
Auth errors and hammer ping FAIL

Expected results:
No errors, correct generation of /etc/tomcat/cert-users.properties

Additional info:
Comment 7 Radek Mynar 2023-01-27 17:37:37 UTC 
I tested various combinations of ST, OU and also few other cert parameters. No combination went to failing 'hammer ping'.

In case of empty 'state' parameter there was an unclear error message - new bug 2165107 created.

VERIFIED with Satellite 6.13 SNAP7.0 @RHEL8.7
Comment 10 errata-xmlrpc 2023-05-03 13:20:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2097
Note You need to log in before you can comment on or make changes to this bug.