Key archival via pki kra-key-archive generate audit events in the wrong order. For example:
$ pki -d /root/.dogtag/pki-tomcat/ca/alias -c Secret.123 -n caadmin \ kra-key-archive --clientKeyID test --passphrase secret
The command generates the following logs:
[AuditEvent=SECURITY_DATA_ARCHIVAL_REQUEST_PROCESSED][SubjectID=kraadmin][Outcome=Success][ArchivalRequestID=<null>][RequestId=44][ClientKeyID=test][KeyID=16][FailureReason=None][PubKey=<null>] security data archival request processed [AuditEvent=SECURITY_DATA_ARCHIVAL_REQUEST][SubjectID=kraadmin][Outcome=Success][ArchivalRequestID=<null>][RequestId=44][ClientKeyID=test] security data archival request made
Ideally the SECURITY_DATA_ARCHIVAL_REQUEST should happen before SECURITY_DATA_ARCHIVAL_REQUEST_PROCESSED.
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 @mharmsen: - Custom field proposedmilestone adjusted to 10.5 (was: None) - Custom field proposedpriority adjusted to critical (was: None) - Issue assigned to edewata
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Per meeting of 20171113 - 10.5 - critical
Metadata Update from @mharmsen: - Custom field proposedmilestone adjusted to None (was: 10.5)
Per CS/DS Meeting of 20180122: FUTURE
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.5)
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/2969
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)