#2613 CMC: id-cmc-identityProofV2 feature implementation
Closed: fixed 7 years ago Opened 7 years ago by mharmsen.

Provide feature relating to id-cmc-identityProofV2 as specified in new CMC rfc
5272

This feature will provide the underlying mechanism for Proof Of Origin for at the minimum the signing cert requests.

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;


Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1419734

7 years ago

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1419734

7 years ago

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

7 years ago

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)

7 years ago

commit 5f2d025962afa34deca93c3b46ff374376c0ea43
Author: Christina Fu cfu@redhat.com
Date: Sat Feb 18 12:27:49 2017 -0800

Bug 1419734 CMC: id-cmc-identityProofV2 feature implementation This patch adds both client and server support for two cmc controls: id-cmc-identityProofV2 - for supporting RFC5272, and id-cmc-identification - for assisting in shared secret search; Note: for client, only CMCRequest is updated in this patch

Metadata Update from @cfu:
- Issue assigned to cfu
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4.1 (was: 10.4)

7 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.4.1-1.fc27

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

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