foreman_scap_client fails with 'SL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed'

Solution Verified - Updated -

Environment

  • Red Hat Satellite v 6.1.5
  • Openscap

Issue

  • foreman_scap_client fails with,
# /usr/bin/foreman_scap_client 1
File /var/lib/openscap/content/1fbdc87d24db51ca184419a2b6f7018f1361c27cd818755d5bc4f5b08fed0a7c.xml is missing. Downloading it from proxy
Download scap content xml from: https://satellite.example.com:5674/compliance/policies/1/content
SCAP file is missing and download failed with error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

Resolution

  • Check the configuration file /etc/foreman_scap_client/config.yaml and confirm if the below entry is correct for ":ca_file:" ,
:ca_file: '/etc/rhsm/ca/katello-server-ca.pem'

For more KB articles/solutions related to Red Hat Satellite 6.x OpenSCAP Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x OpenSCAP Issues

Root Cause

  • Configuration file for openscap /etc/foreman_scap_client/config.yaml on client was incorrectly configured with the entries,
:ca_file: '/var/lib/puppet/ssl/certs/ca.pem'
:host_certificate: '/var/lib/puppet/ssl/certs/myhost.example.com.pem'
:host_private_key: '/var/lib/puppet/ssl/private_keys/myhost.example.com.pem'

When really it should be:

:ca_file: '/etc/rhsm/ca/katello-server-ca.pem'
:host_certificate: '/etc/pki/consumer/cert.pem'
:host_private_key: '/etc/pki/consumer/key.pem'

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments