Bug 2052077

Description of problem:
If somehow the permissions of the file /etc/foreman-proxy/ssl_ca.pem are wrong in a way that the user foreman-proxy can't read it, multiple services will stop working due to the impossibility for the foreman-proxy daemon to validate client certificates sent by foreman when trying to communicate with it.

However, the error that will be returned is completely misleading only saying that it's unable to get local issuer certificate when in fact it simply can't read a file.


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

I check on Satellite 6.10 (foreman-proxy-2.5.2-1.el7sat.noarch) and Satellite 6.9 (foreman-proxy-2.3.1-1.el7sat.noarch)

How reproducible:

Always

Steps to Reproduce:
1. Change the permissions of the file /etc/foreman-proxy/ssl_ca.pem:

~~~
chmod 600 /etc/foreman-proxy/ssl_ca.pem
~~~

2. Restart foreman-proxy service:

~~~
systemctl restart foreman-proxy
~~~

3. Try making a request that needs certificate validation:

~~~
#  curl --cacert /etc/foreman/proxy_ca.pem --cert /etc/foreman/client_cert.pem --key /etc/foreman/client_key.pem https://$(hostname -f):9090/logs
curl: (35) Peer does not recognize and trust the CA that issued your certificate.
~~~

Actual results:
Returns an SSL error to the user and to the logs.


Expected results:
Return an generic SSL error to the user, but on the logs it should be clear that the file couldn't be read.


Additional info: