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.

The smart-proxy-abrt (and possibly other plugins, like openscap) needs to send HTTP requests to Foreman, and for that it needs to be SSL-authenticated. However the cert+key in /etc/foreman-proxy/ssl_{cert,key}.pem cannot be used because it is designated as a server certificate and Apache rejects it when it is used for client authentication.

We can reuse the cert+key pair in /etc/puppet, however smart-proxy currently does not have the permissions to access the private key.

1) Can you copy /etc/puppet/{client_cert,client_key,ssl_ca.pem} to /etc/foreman-proxy with permissions so that smart-proxy can read them? (On my system /etc/puppet/ssl_ca.pem is the same as /etc/foreman-proxy/ssl_ca.pem so no need to have it twice if it's always the case)

2) Can you then assign the paths to the files to @foreman_ssl_cert@, @foreman_ssl_key@, and @foreman_ssl_ca@ in /etc/foreman-proxy/settings.yml?

Created from redmine issue http://projects.theforeman.org/issues/8372

Setting as blocker since abrt and openscap integration depends on that

Upstream bug assigned to inecas

Moving to POST since upstream bug http://projects.theforeman.org/issues/8372 has been closed
-------------
Ivan Necas
Fixes that generate and deploy a cert for smart proxy to use to call to the foreman are here:

https://github.com/theforeman/puppet-foreman_proxy/pull/130
https://github.com/Katello/puppet-certs/issues/41
https://github.com/Katello/puppet-capsule/issues/26
-------------
Martin Milata
> https://github.com/theforeman/puppet-foreman_proxy/pull/130
> https://github.com/Katello/puppet-certs/issues/41
> https://github.com/Katello/puppet-capsule/issues/26

I've tested the changes on single-host Katello installation and the ABRT plugin now works out-of-the-box (with the exception of #7833 which has to be done manually).

Tested generating openscap reports on clients and uploading it using custom-certs on both "Internal capsule" and "external capsule".

VERIFIED with sat6.1.1-GA-snap13-c1

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, 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-2015:1592