Description of problem: When handling GetCACert requests, the logic currently doesn't attempt to return an application/x-x509-ca-ra-cert PKCS#7 blob when the RA's certifying chain has more than one certificate in it. Unless a client "knows" to start with "message" set to 0 and attempt to walk the certifying chain, it will not be able to retrieve all of the certificates which are needed in order to successfully interact with the server.
Version-Release number of selected component (if applicable): pki-common-9.0.3-38.el6_6.noarch
https://bugzilla.redhat.com/show_bug.cgi?id=1198262
Metadata Update from @cipherboy: - 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1198262 - Custom field type adjusted to None - Custom field version adjusted to None
Duplicate of https://pagure.io/dogtagpki/issue/1299
Metadata Update from @cipherboy: - Issue close_status updated to: duplicate - Issue status updated to: Closed (was: Open)
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/3280
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.