PIN_RESET policy is not giving expected results when set on a token

[pki-bot]

This issue was migrated from Pagure Issue #2510. Originally filed by rpattath (@rpattath) on 2016-10-10 17:52:34:

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

---

PIN_RESET policy is not giving expected results when set on a token

Steps to Reproduce:

1. Add the following to the token policy using TPs Web UI
PIN_RESET=NO
2. Reset pin on a token

Actual results:

Pin reset operation is successful

Expected results:

Pin reset operation should not be allowed

Additional info:

Also tried the policy RESET_PIN_RESET_TO_NO, that wcryptomilk't working as expected
either.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-10-18 23:30:37

Per PKI Bug Council of 10/18/2016: 10.3

[pki-bot]

Comment from jmagne (@jmagne) at 2016-10-21 20:17:08

commit 8c15e8d
Author: Jack Magne jmagne@dhcp-16-206.sjc.redhat.com
Date: Tue Oct 18 18:58:21 2016 -0700

PIN_RESET policy is not giving expected results when set on a token.

Simple fix to actually honor the PIN_RESET=<YES>or<NO> policy for a given token.

Ticket 2510.

Closing

[pki-bot]

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

Metadata Update from @rpattath:

• Issue set to the milestone: 10.3.8