#2803 CMCRequest: self-signed cmc request has ASN.1 Error: Object has zero length
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

CMCRequest: self-signed cmc request has ASN.1 Error: Object has zero length
I have observed that it happens to every self-signed cmc request, but not others. Although the requests still get processed by the CA without issues.

Steps to Reproduce:

Generate a cmcrequest for self signed certificate http://pki.fedoraproject.org/wiki/PKI_10.4_CMC_Feature_Update_%28RFC5272%29#Self-Signed_CMC_Request_Example_.28with_IdentityProofV2.29

Expected results:

Need to understand why we get this and how to resolve it?

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1474675
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue priority set to: major
- Issue set to the milestone: 10.5

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

Per 10.5.x/10.6 Triage: 10.6

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

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.

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

3 years ago

Login to comment on this ticket.

Metadata