Inconsistent SECURITY_DATA_ARCHIVAL_REQUEST outcomes.

dogtagpki / pki

The Dogtag Certificate System is an enterprise-class Certificate Authority (CA) which supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management.

https://www.dogtagpki.org

GNU General Public License v2.0

373 stars 137 forks source link

Inconsistent SECURITY_DATA_ARCHIVAL_REQUEST outcomes. #2968

Open pki-bot opened 4 years ago

pki-bot commented 4 years ago

This issue was migrated from Pagure Issue #2848. Originally filed by edewata (@edewata) on 2017-11-01 14:21:28:

Assigned to edewata (@edewata)
Associated bugzillas
- https://bugzilla.redhat.com/show_bug.cgi?id=1539200

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.

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-01 19:57:17

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

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-09 19:20:45

Metadata Update from @mharmsen:

Issue assigned to edewata

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-09 19:21:44

Metadata Update from @mharmsen:

Custom field proposedmilestone adjusted to 10.5 (was: None)
Custom field proposedpriority adjusted to critical (was: None)

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-14 11:48:08

Per meeting of 20171113 - 10.5 - critical

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-14 11:48:09

Metadata Update from @mharmsen:

Issue priority set to: critical
Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2017-11-14 11:49:16

Metadata Update from @mharmsen:

Custom field proposedmilestone adjusted to None (was: 10.5)

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2018-01-26 16:57:10

Metadata Update from @mharmsen:

Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539200

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2018-04-19 21:08:39

Per 10.5.x/10.6 Triage: 10.5.x

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2018-05-04 20:43:46

Metadata Update from @mharmsen:

Issue priority set to: major (was: critical)

celestian commented 1 year ago

This issue is related to clear audit topic.