TPS fails to recover additional certs when the token already has a recovered cert/key
Steps to Reproduce:
1. add an user to TPS dn: uid=pkiuser3,ou=People,dc=pki-tps1 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:: e1NTSEF9RUtXZzJUSGtzR0NEYzIzNzNIUlc3VzVJNGZ2VncrOHRxK1JQNUE9PQ= = tokenType: externalRegAddToToken certstoadd: 64,ca1 certstoadd: 65,ca1,13,kra1 cert with (decimal) serial number 64 has already been recovered on the token cert with serial 65 is the additional cert that needs to be recovered. 2. Enroll a smartcard authenticating as user pkiuser3
Actual results:
enrollment fails, ESC shows the error message "ESC lost connection to smartcard server)
Expected results:
enrollment should be successful, cert/key should be recovered on the token
Additional info:
Attaching TPS debug log to Bugzilla Bug.
This feature will be covered by: https://fedorahosted.org/pki/ticket/1375, target 10.3.
Metadata Update from @rpattath: - Issue set to the milestone: 10.3.0
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/2068
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.