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 798454 - SSLCACertificateFile not set properly in /etc/httpd/conf.d/pulp.conf
Summary: SSLCACertificateFile not set properly in /etc/httpd/conf.d/pulp.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 21:42 UTC by Justin Sherrill
Modified: 2019-09-26 15:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:29:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Justin Sherrill 2012-02-28 21:42:26 UTC
Description of problem:

As part of the install/configuration, SSLCACertificateFile is not set properly in /etc/httpd/conf.d/pulp.conf.  This should be set to the same thing as in /etc/pulp/pulp.conf (/etc/candlepin/certs/candlepin-ca.crt)

The result of all this is that the uber cert does not work for debugging withou this change.  The browser is never prompted to use the ubercert.

Came about from: https://bugzilla.redhat.com/show_bug.cgi?id=798418

Comment 2 Lukas Zapletal 2012-03-02 11:14:50 UTC
Okay.

Comment 3 Lukas Zapletal 2012-03-02 11:42:44 UTC
Pushing upstream, waiting for PM ack.

b6fbd05 798454 - SSLCACertificateFile not set properly

Comment 4 Lukas Zapletal 2012-03-02 16:23:21 UTC
Ther is also one in the ssl.conf but I believe this is not used.

Comment 6 Og Maciel 2012-03-06 19:13:03 UTC
Lukáš, this is what I see right now:

[root@qetello03 ~]# grep "SSLCACertificateFile" /etc/httpd/conf.d/pulp.conf
SSLCACertificateFile /etc/pki/pulp/ca.crt
[root@qetello03 ~]# vim /etc/pulp/pulp.conf
[security]
cacert:  /etc/candlepin/certs/candlepin-ca.crt
cakey:   /etc/candlepin/certs/candlepin-ca.key
user_cert_expiration: 7
consumer_cert_expiration: 3650

fwiw here's the version for katello-configure: katello-configure-0.1.101-1.el6.noarch

Comment 8 Og Maciel 2012-03-09 15:49:03 UTC
Verified:
* candlepin-0.5.24-1.el6.noarch
* candlepin-tomcat6-0.5.24-1.el6.noarch
* katello-0.1.303-1.el6.noarch
* katello-all-0.1.303-1.el6.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.0.4-1.el6.noarch
* katello-cli-0.1.102-1.el6.noarch
* katello-cli-common-0.1.102-1.el6.noarch
* katello-common-0.1.303-1.el6.noarch
* katello-configure-0.1.104-1.el6.noarch
* katello-glue-candlepin-0.1.303-1.el6.noarch
* katello-glue-foreman-0.1.303-1.el6.noarch
* katello-glue-pulp-0.1.303-1.el6.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-0.1.8-1.el6.noarch
* pulp-1.0.0-4.el6.noarch
* pulp-common-1.0.0-4.el6.noarch
* pulp-selinux-server-1.0.0-4.el6.noarch


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