Encryption cert recovered on a temporary token has different status under temporary token and lost token
Steps to Reproduce:
1. Format and enroll a token for user1 2. Mark the token temp lost 3. Format and enroll a temporary token for the same user
Actual results:
Encryption cert on the lost token is recovered on the temp token. CA and temp token under TPS shows an "Active" status for the encryption cert but the lost token under TPS still shows a "revoked_on_hold" status
Expected results:
The cert should have the same status at all three places.
Additional info:
Attaching the TPS debug log info (in associated bug) during show certificate action for each token
Metadata Update from @rpattath: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
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 priority set to: 3 - Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)
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/2712
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)