#2759 Automatic key recovery : GenerateNewKeyAndRecoverLast does not work with terminated token
Closed: migrated 4 years ago by dmoluguw. Opened 7 years ago by mharmsen.

Automatic key recovery : GenerateNewKeyAndRecoverLast does not work with terminated token

Steps to Reproduce:

1. Make changes to TPS CS.cfg as follows
op.enroll.userKey.keyGen.encryption.recovery.terminated.scheme=GenerateNewKeyAndRecoverLast

2. Mark an enrolled token terminated
3. Issue a new token for the user

Actual results:

New certs are issued on the new token but the old encryption cert is not recovered

Expected results:

New certs should be issued and old encryption cert recovered.

Additional info:

TPS debug log is attached to 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 type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

7 years ago

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1464514

7 years ago

Metadata Update from @mharmsen:
- Issue assigned to jmagne

7 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

7 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

7 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

7 years ago

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata