ESC lists a recovered signing cert/key on a token as encryption key
Steps to Reproduce:
1. Make the following changes to TPS config externalReg.enable=true op.enroll.userKey.keyGen.signing.serverKeygen.archive=true op.enroll.userKey.keyGen.signing.serverKeygen.drm.conn=kra1 op.enroll.userKey.keyGen.signing.serverKeygen.enable=true 2. Enroll a smartcard token with the following user (externalRegAddtoToken tokentype) dn: uid=pkiuser3,ou=People,dc=pki-ca-Jun21-CA objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: top objectClass: extensibleobject cn: pkiuser3 sn: pkiuser3 uid: pkiuser3 givenName: pkiuser3 mail: pkiuser3@example.org firstname: pkiuser3 userPassword: redhat certstoadd: 56063789,ca1,55,kra1 - encryption cert and key certstoadd: 11403942,ca1,60,kra1 - signing cert and key
Actual results:
ESC list the signing key recovered onto the token as encryption key
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1465149 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (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/2882
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)