#2488 KRA key recovery fails with Key Identifiers when KRA is configured
Closed: worksforme Opened by ssidhaye@redhat.com.

Key recovery with Key Identifiers fails when KRA is configured with lunaSA

Steps to Reproduce:

1. Generate a certificate request which archives the key
2. Approve the certificate request
3. From the Recovery section in KRA page select Key Identifiers and Show Key
4. Select Recover option from the results

Actual results:

Key recovery fails with the following message:
"Problem processing your request"
"certificate not found"

Expected results:

Key recovery should succeed.

Additional info:

Key recovery with certificate is working as expected. I am able to recover the
key with a certificate.

Per CS/DS meeting of 10/3/2016: 10.4

  • dropped lunaSA from Summary
  • has a workaround -- requested in associated bug

Metadata Update from @ssidhaye@redhat.com:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue priority set to: 2 (was: 3)
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

Per PKI Bug Council of 04/05/2017: CLOSING CURRENT RELEASE (QE RE-TEST)

Since this issue has morphed throughout its existence, it was determined that it should be closed and re-tested by QE.

QE will file new issues if any problems still persist.

Metadata Update from @mharmsen:
- Issue close_status updated to: worksforme
- Issue set to the milestone: 10.4.2 (was: 10.4)
- 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/2608

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata