#2616 CMC: replace id-cmc-statusInfo with id-cmc-statusInfoV2
Closed: fixed 6 years ago Opened 7 years ago by mharmsen.

This is a general task to replace existing id-cmc-statusInfo with
id-cmc-statusInfoV2 as required by rfc 5272.

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=1419747

7 years ago

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

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

Metadata Update from @cfu:
- Issue assigned to cfu

6 years ago

commit 5188d4f195b068c10a4ae24b0af63456f5242ee4
Author: Christina Fu cfu@redhat.com
Date: Fri Jun 16 18:20:38 2017 -0700

commit 6273907e0ca36425fa30c106b7fdd28c510b1162
Author: Christina Fu cfu@redhat.com
Date: Fri Jun 16 18:20:38 2017 -0700

Ticket #2616 CMC: id-cmc-statusInfo ==> id-cmc-statusInfoV2

This patch contains the following update:
* Structurely, CMCStatusInfo to CMCStatusInfoV2 update; no extendedFailInfo has been added at this point
* In case of EncryptedPOP, instead of returning with CMCStatus pending where
  PendInfo contains the requestID, it now returns CMCStatus failed whith
  responseInfo control contains the requestID. On the client side, CMCRequest
  now processes the responseInfo and returns the DecryptedPOP with requestID in
  the regInfo control. CMCResponse has been updated to handle the new controls
  as well.
* A number of fail info codes are now being supported by the server to add
  clarity to CMC failed status, including:
  badMessageCheck, badRequest, unsuportedExt, badIdentity, popRequired, and popFailed.

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

6 years ago

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

6 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/2736

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