dogtagpki

#2663 Misleading audit log for certificate request rejected by agent.
Closed: duplicate Opened by edewata.

Closed: duplicate
Reopen Issue

When an agent rejects a certificate request the server will trigger a CERT_REQUEST_PROCESSED audit event with a Success outcome. From agent's perspective the request is processed, so a Success is correct. However, from auditor/user's perspective the certificate is not issued (i.e. not processed), so the outcome should have been a Failure.

Steps to reproduce:
1. Install CA
2. Submit a cert request
3. As an agent, reject the request. With PKI CLI it can be done with the following command:

$ pki -d ~/.dogtag/pki-tomcat/ca/alias/ -c Secret.123 -n caadmin ca-cert-request-review 7 --action reject

Actual result: The server will generate the following audit log:

[AuditEvent=CERT_REQUEST_PROCESSED]
    [SubjectID=caadmin]
    [Outcome=Success]
    [ReqID=7]
    [InfoName=rejectReason]
    [InfoValue=<null>]
    certificate request processed

Expected result: The outcome for certificate request rejected by agent should be a Failure.

As a comparison, when a certificate is rejected due to profile violation, the outcome is a Failure:

[AuditEvent=CERT_REQUEST_PROCESSED]
    [SubjectID=$NonRoleUser$]
    [Outcome=Failure]
    [ReqID=7]
    [InfoName=rejectReason]
    [InfoValue=Request 7 Rejected - Subject Name Not Matched UID=testuser]
    certificate request processed

See also http://pki.fedoraproject.org/wiki/CA_Audit_Events.

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 set to the milestone: 0.0 NEEDS_TRIAGE

Metadata Update from @mharmsen:
- Issue priority set to: ---

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

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

Issue linked to Bugzilla: Bug 1446366

Per PKI Bug Council of 04/27/2017: 10.4 - critical

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

Metadata Update from @mharmsen:
- Issue assigned to edewata

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

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

Per CS/DS Meeting 09/25/2017: 10.5 critical
Edited by mharmsen

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

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

Metadata Update from @edewata:
- Assignee reset

See also tickets #2690 and #2838.

This was actually already fixed in PKI 10.4 in the following tickets:

  • https://pagure.io/dogtagpki/issue/2693
  • https://pagure.io/dogtagpki/issue/2694

If the current behavior is incorrect, please define the correct behavior in this ticket:

https://pagure.io/dogtagpki/issue/2838
Edited by edewata

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

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

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

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
None
None
None
None
Low
Community
defect
General
''
''
''
''
''
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.