#2510 PIN_RESET policy is not giving expected results when set on a token
Closed: Fixed None Opened 7 years ago by rpattath.

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 wasn't working as expected
either.

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

commit 8c15e8d60a4004cb63ebb0bf2bed73be919d54ee
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

Metadata Update from @rpattath:
- Issue set to the milestone: 10.3.8

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

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.

Login to comment on this ticket.

Metadata