Re-enroll of a smartcard token does not revoke the original certificates on the token

[pki-bot]

This issue was migrated from Pagure Issue #2545. Originally filed by rpattath (@rpattath) on 2016-11-16 19:19:44:

• Closed as invalid
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1394020

---

Re-enroll of a smartcard token does not revoke the original certificates on the
token

Steps to Reproduce:

1. Using the default TPS CS.cfg, re-enroll a token

Actual results:

The original certificates on the smartcard are not revoked, new certificates
are issued for the token

Expected results:

The original certificates on the smartcard must be revoked, new certificates
are issued for the token

Additional info:

debug log file attached to associated Bugzilla Bug

[pki-bot]

Comment from cfu (@cfu) at 2016-11-19 02:03:51

You said "Using the default TPS CS.cfg", and you did not say anything about setting the token policy.
The default token policy is:
tokendb.defaultPolicy=RE_ENROLL=YES;RENEW=NO;FORCE_FORMAT=NO;PIN_RESET=NO;RESET_PIN_RESET_TO_NO=NO

Since by default "FORCE_FORMAT=NO", which means during re-enrollment, the token is not formatted; And if it is not formatted, it would not follow the rules set by
op.format..revokeCert=true

So unless I missed something, it seems to be behaving exactly as expected.

I'm setting this bug to Invalid; You can change it again if I did miss something. And if so, please explain in more detail with more specific relevant configuration.

[pki-bot]

Comment from rpattath (@rpattath) at 2017-02-27 14:00:14

Metadata Update from @rpattath:

• Issue set to the milestone: 0.0 NEEDS_TRIAGE

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-03-14 18:52:52

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: invalid (was: Invalid)
• Issue set to the milestone: 10.4.0 (was: 0.0 NEEDS_TRIAGE)