Certificate status mismatch on CA and TPS token db
Steps to Reproduce:
1. Enroll a token using userKey token type and default TPS CS.cfg 2. Make changes to TPS needed for externalReg using userKey token type 3. Recover cert/key on the token in step 1 using userKey token type 4. Format the token (recovered cert on the token is revoked because of op.format.userKey.revokeCert=true) 5. Change the status of the token in step 1 to temporarily lost. 6. Change the status of the token in step 1 to token found
Actual results:
TPS token db has certificate status active and CA has status revoked
Expected results:
Mismatch in status not expected
Additional info:
The TPS debug log is attached to the associated bug.
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=1451871 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue assigned to cfu - Issue priority set to: critical
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/2817
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.