Dogtag needs to record complete (signed or otherwise) CMC requests and signed responses. It can be done in either of the following:
Metadata Update from @cfu: - 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=1525306 - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue assigned to cfu
up for review: https://review.gerrithub.io/398136
commit 55a6fa09d24b1c30bfd9d80357d69a8905ee4090 Author: Christina Fu cfu@redhat.com Date: Thu Feb 1 18:37:10 2018 -0800
Ticket #2880 missing CMC request and response record This patch adds audit events to record received CMC requests and signed CMC responses: CMC_REQUEST_RECEIVED CMC_RESPONSE_SENT This patch fixes https://pagure.io/dogtagpki/issue/2880 Change-Id: Id093225b22a2c434e680726442c49b410fa738a3
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.5.5 (was: 10.5)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.5-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/2999
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.