dogtagpki

#2848 Inconsistent SECURITY_DATA_ARCHIVAL_REQUEST outcomes.
Closed: migrated by dmoluguw. Opened by edewata.

Closed: migrated
Reopen Issue

The following scenarios will generate SECURITY_DATA_ARCHIVAL_REQUEST events with different outcomes:

  • When a CRMF request is submitted with a wrong transport certificate using CRMFPopClient or pki client-cert-request, it will generate a Failure outcome.
  • When a key is archived with a wrong transport certificate using pki kra-key-archive, it will generate a Success outcome.

These scenarios should produce the same outcomes since the cause of the problem is the same.

See also ticket #2792.

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 type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Metadata Update from @mharmsen:
- Issue assigned to edewata

Metadata Update from @mharmsen:
- Custom field proposedmilestone adjusted to 10.5 (was: None)
- Custom field proposedpriority adjusted to critical (was: None)

Per meeting of 20171113 - 10.5 - critical

Metadata Update from @mharmsen:
- Issue priority set to: critical
- Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)

Metadata Update from @mharmsen:
- Custom field proposedmilestone adjusted to None (was: 10.5)

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

Per 10.5.x/10.6 Triage: 10.5.x

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

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

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)
Metadata
None
None
None
Normal
None
None
None
None
None
None
critical
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.