Steps to Reproduce:
1. Add the following to the token policy using TPs Web UI PIN_RESET=YES;RESET_PIN_RESET_TO_NO=YES 2. Attempt reset pin operation on a token twice
Actual results:
Both attempts are successful
Expected results:
Second attempt should fail
Additional info:
The debug log is attached to the associated bug. No other changes were made to the TPS config
Per PKI Bug Council meeting of 11/03/2016: 10.3
Per PKI Bug Council of 11/29/2016: 10.4 - critical
Metadata Update from @rpattath: - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
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/2653
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)
Login to comment on this ticket.