This task should allow both signing and non-signing cmc revocation cert requests to be signed by a previously-issued signing certificate of the same subjectDN.
The server should be able to
This task might be companioning task for https://pagure.io/dogtagpki/issue/2617 and https://pagure.io/dogtagpki/issue/2618 (same assignee is recommended)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1419777
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: 2
Metadata Update from @mharmsen: - Custom field component adjusted to CMC (was: General) - Custom field origin adjusted to RHCust (was: Community) - Custom field type adjusted to enhancement (was: defect)
Metadata Update from @cfu: - Issue assigned to cfu
commit 698192f4f62c55142a557f6489ed2323e17401b0 Author: Christina Fu cfu@redhat.com Date: Tue May 30 14:12:06 2017 -0700
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.8 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: blocker (was: critical)
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/2739
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.