CertGuard

Ticket moved to GitHub: "pulp/pulp-certguard/145":https://github.com/pulp/pulp-certguard/issues/145

(Copied from BZ)

When a client is denied access by the rhsm-certguard, the log messages describing the reason are lost with log level debug. They should be raised to at least warning, because they tell an administrator, why a client is unable to consume their subscriptions.

Steps to Reproduce:

1. Subscribe a host to RH subscription content
2. Find a reason for the rhsm content guard to reject the client certificate Either https://bugzilla.redhat.com/show_bug.cgi?id=1977893, or misconfigure it, see below
3. On the host run yum update and observe that repodata.xml returns 403
4. In forman-tail observe that all reasons for ^ are in log level DEBUG

Expected results:
Failed authentication to subscription content should be logged at a higher level, maybe WARNING.

Additional info:
Misconfiguring may be:
curl -vv -k -X PATCH --data-urlencode 'ca_certificate@fake.crt' --cert /etc/pki/katello/certs/pulp-client.crt --key /etc/pki/katello/private/pulp-client.key "https://localhost/pulp/api/v3/contentguards/certguard/rhsm/<UUID>/"