PKI server has two different OCSP signing certificates with slightly different extensions. They should be consistent.
The OCSP signing certificate in CA subsystem has the following extensions:
Signed Extensions: Name: Certificate Authority Key Identifier Key ID: 21:6b:08:30:25:3e:e4:f1:72:47:23:bc:ab:a0:09:c8: a0:7f:44:0b Name: Certificate Key Usage Critical: True Usages: Digital Signature Non-Repudiation Certificate Signing CRL Signing Name: Authority Information Access Method: PKIX Online Certificate Status Protocol Location: URI: "http://server.example.com:8080/ca/ocsp" Name: Extended Key Usage OCSP Responder Certificate
The OCSP signing certificate in OCSP subsystem has the following extensions:
Signed Extensions: Name: Certificate Authority Key Identifier Key ID: 21:6b:08:30:25:3e:e4:f1:72:47:23:bc:ab:a0:09:c8: a0:7f:44:0b Name: Authority Information Access Method: PKIX Online Certificate Status Protocol Location: URI: "http://server.example.com:8080/ca/ocsp" Name: Extended Key Usage OCSP Responder Certificate Name: OCSP No Check Extension Data: NULL
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @vakwetu: - Issue priority set to: critical - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Two things we want in each OCSP signing certificate: 1. the OCSP signing Extended Key Usage: OID: 1.3.6.1.5.5.7.3.9 2. the id-pkix-ocsp-nocheck extension OID: 1.3.6.1.5.5.7.48.1.5
It appears that under .../profiles/ca, the two OCSP profiles have them: caOCSPCert.cfg caInternalAuthOCSPCert.cfg
while in .../conf/caOCSPCert.profile, it's missing the id-pkix-ocsp-nocheck extension. and that happens to be the profile used for generating OCSP signing cert that's internal to the CA.
Metadata Update from @edewata: - Issue assigned to edewata
Code review:
Fixed in master:
Metadata Update from @edewata: - Issue set to the milestone: 10.5.1 (was: 10.5)
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.1-1.fc27
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2938
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.