Provide feature relating to id-cmc-popLinkWitnessV2 as specified in new CMC rfc 5272
This feature will provide the some of the underlying mechanism for Proof of Possession.
This task should complete the server-side implementation; at least one client-side tool as well as enrollment profile (if needed) should be provided to allow testing;
This task will depend on the availability of completed work for underlying JSS ASN.1 code from https://bugzilla.mozilla.org/show_bug.cgi?id=1337092.
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1419737
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: 2
Metadata Update from @mharmsen: - Custom field component adjusted to CMC (was: General) - Custom field origin adjusted to RHCust (was: Community) - Custom field type adjusted to enhancement (was: defect)
Metadata Update from @cfu: - Issue assigned to cfu
commit b04739d364e7e220da29ce8d47654377999ad881 Author: Christina Fu cfu@redhat.com Date: Thu Apr 13 16:53:58 2017 -0700
Ticket #2614 CMC: id-cmc-popLinkWitnessV2 feature implementation This patch provides the feature for CMC on handling id-cmc-popLinkWitnessV2
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.2 (was: 10.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/2734
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.