The OCSP server currently accepts multiple CA's CRLS but can only sign it with one single ocsp singing cert.
The way clients validate ocsp response is by checking its signer to see if it is signed directly by the CA of the cert in question.
We should support multiple ocsp singing certs, one each for each CA it supports.
From IRC conversation of 10/20/2015 - 10.4 - major
Metadata Update from @dminnich:
- Issue set to the milestone: UNTRIAGED
some info from Bob:
You may still have an issue with a single OCSP server serving multiple
CA's. The certificate for the OCSP server must either be the CA itself,
or a cert signed directly by the CA with appropriate extension. The OCSP
server would have to select the correct OCSP cert to return with the
request (multiple OCSP certs can have the same key and therefore work
with the single OCSP server). So it's possible, but you'll need to issue
multiple OCSP certs for the same key (as well as the OCSP server
selecting the correct cert based on the request).
Metadata Update from @cfu:
- Custom field feature adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
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:
If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
to comment on this ticket.