SCP02 token re-enrollment fails
Steps to Reproduce:
https://bugzilla.redhat.com/show_bug.cgi?id=1097352#c19
Actual results:
Re-enrollment fails
Expected results:
Re-enrollment should be successful and the token should have the new certs
Per CS/DS Meeting of 08/17/2015 - 10.3 [critical]
Per PKI Bug Council of 06/23/2016: 10.4
We shoudl test this with SCP03 when it is done. We've already put in code to set the lifecycle value if it needs to be set. That code should solve this problem as well.
Metadata Update from @rpattath: - Issue set to the milestone: 10.4
Per PKI Bug Council of 04/06/2017: FUTURE
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: None - Issue set to the milestone: FUTURE (was: 10.4)
SCP02 is no longer supported. So, this won't be fixed.
Metadata Update from @dmoluguw: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/2113
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.