Recovered certs on a smartcard token have the same nickname
Steps to Reproduce:
1. Recover 2 encryption certs on a smartcard token using external registration
Actual results:
[root@dhcp129-54 ~]# certutil -K -d /etc/pki/nssdb/ -h pkiuser3 certutil: Checking token "pkiuser3" in slot "OMNIKEY AG CardMan 3021 00 00" Enter Password or Pin for "pkiuser3": < 0> rsa 00 encryption key for pkiuser3 < 1> rsa 01 encryption key for pkiuser3 [root@dhcp129-54 ~]# certutil -L -d /etc/pki/nssdb/ -h pkiuser3 Certificate Nickname Trust Attributes SSL,S/MIME,JAR/XPI Enter Password or Pin for "pkiuser3": pkiuser3:encryption key for pkiuser3 u,u,u pkiuser3:encryption key for pkiuser3 u,u,u
Expected results:
the nickname of the cert should have the uid/cn associated with the cert
Per PKI Bug Council of 10/10/2016: 10.4
Metadata Update from @rpattath: - 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 set to the milestone: 10.4 (was: UNTRIAGED)
Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.
Metadata Update from @mharmsen: - Issue set to the milestone: FUTURE (was: 10.4)
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/2624
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)
Login to comment on this ticket.