dogtagpki

#1515 TPS UI: After successful key upgrade during pin reset operation the token db still shows old key
Closed: Fixed Opened by rpattath.

Closed: Fixed
Reopen Issue

TPS UI: After successful key upgrade during pin reset operation the token db
still shows old key

Steps to Reproduce:

1. Perform keychange over of a token during pin reset operation 0101 to 0201

Actual results:

Pin reset is successful. not seeing any failures in the TPS or TKS debug log.
TPS UI shows 0101

Expected results:

TPS UI should show 0201

Additional info:

Debug log attached to corresponding Bugzilla Bug.

commit e50a3d55017da97abb5296218422b4144c8ca990
Author: Jack Magne jmagne@localhost.localdomain
Date: Tue Jul 28 15:29:35 2015 -0700

TPS UI: After successful key upgrade during pin reset operation the token db still shows old key
Simple matter of not updating the token record at the end of the pin reset operation.
Also, make sure the activity log is correct.

Modified in 10.2.6-4.

Metadata Update from @rpattath:
- Issue set to the milestone: 10.2.6

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/2074

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
None
None
None
None
Normal
defect
TPS
QE
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.