Issue #8783
closed
CA certificate does not handle a CA bundle or chain file correctly
Status:
CLOSED - CURRENTRELEASE
Description
If I set the value of ca_certificate (e.g. update certguard_rhsmcertguard SET ca_certificate = :'content' ;) where that content is a bundle of CA certificates, clients will receive a 403 unless the CA that signed the client certificate is the first CA in the file.
Thanks, we definitely want to get this working. Right now the feature set has 100% functional test coverage with certs we got from katello last time. Would it be possible for katello to provide cert/CA data we could test with? We keep it all here: https://github.com/pulp/pulp-certguard/tree/master/pulp_certguard/tests/functional/artifacts
Also can you outline the test we should run, maybe just a more detailed description of the usage along with references to the CA and cert files provided?
@eric wdyt?
- Status changed from NEW to ASSIGNED
- Assignee set to ggainey
- Sprint set to Sprint 99
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- Sprint/Milestone set to 1.4.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Taught CertGuard ca_certificate to accept a cert-bundle.
Testcase merged here from https://github.com/pulp/pulp-certguard/pull/95 - thanks to ehelms@redhat.com!
closes #8783