#2365 Orphan key is getting generated & is never used to issue certificate
Closed: fixed Opened by gkapoor.

Orphan key is getting generated in the nss db but no certificate exist for that
key.

[root@pki1 ~]# certutil -K -d /var/lib/pki/<testCA>/alias
certutil: Checking token "NSS Certificate DB" in slot "NSS User Private
Key and Certificate Services"
Enter Password or Pin for "NSS Certificate DB":
< 0> rsa      81fa4cfdfea5b78b0368d567ae82ac6b41de84f7   caSigningCert
cert-externalCA CA
< 1> rsa      82a8e63a4464df85c6bf95ec614135393169cd43   (orphan)

Steps to Reproduce:

1. check certutil -K -d /var/lib/pki/<testCA>/alias

Actual results:

Orphan keys exist in nssdb

Expected results:

orphan keys should not exist.

Per PKI Bug Council of 06/23/2016: 10.4

workaround is to remove orphaned key

Metadata Update from @gkapoor:
- Issue set to the milestone: UNTRIAGED

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

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

I think this is already fixed in 10.5.

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.6 (was: 10.6)
- 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/2485

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