I tried using the wrong transport cert to do key archival and found the following in the KRA debug log: [15/Aug/2017:14:33:46][http-bio-8443-exec-2]: KRAService serviceRequest EBaseException:Invalid Private Key
Also, the audit log, I see :0.http-bio-8443-exec-2 - [15/Aug/2017:14:33:46 PDT] [14] [6] [AuditEvent=SECURITY_DATA_ARCHIVAL_REQUEST][SubjectID=CA-dhcp-16-119.sjc.redhat.com-8443][Outcome=Failure][ArchivalRequestID=221][RequestId=54][ClientKeyID=null] security data archival request made
The info in the audit log seems a bit lacking in regards to why it failed.
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
Per CS/DS Meeting 09/25/2017: 10.5 critical
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Code review:
Fixed in master:
Metadata Update from @edewata: - Issue assigned to edewata
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.1 (was: 10.5) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.1-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/2912
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.