Token terminations force revocation of all certificates on the token with little ability to customize that process. This RFE is to add that customization.
Since associated bug was re-opened and moved to 9.1 during QE verification, ticket was re-opened and moved to 10.3.
Per PKI Bug Council of 06/30/2016:
cfu to add parameters; rpattath to re-test
pushed to master
commit 63a58cf51ef2982e8a35eff1f98dd42453e5681e Author: Christina Fu cfu@redhat.com Date: Thu Jun 30 14:03:24 2016 -0700
Ticket #1306 config params: Add granularity to token termination in TPS This patch adds the missing configuration parameters that go with the original bug. The code would take on defaults when these parameters are missing, but putting them in the CS.cfg would make it easier for the administrators
Metadata Update from @mharmsen: - Issue assigned to cfu - Issue set to the milestone: 10.3.4
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/1868
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.
Login to comment on this ticket.