RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1446366 - CC: Misleading audit log for certificate request rejected by agent.
Summary: CC: Misleading audit log for certificate request rejected by agent.
Keywords:
Status: CLOSED DUPLICATE of bug 1452250
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-27 18:29 UTC by Matthew Harmsen
Modified: 2020-10-04 21:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-02 01:33:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2783 0 None None None 2020-10-04 21:27:50 UTC

Description Matthew Harmsen 2017-04-27 18:29:36 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/dogtagpki/issue/2663

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.

Comment 3 Christina Fu 2017-09-21 21:56:19 UTC
I am not sure.  I think it is correct the way it is.

Comment 4 Endi Sukma Dewata 2017-11-02 01:33:03 UTC
This was actually already fixed in RHEL 7.4 in bug #1452250.

If the current behavior is incorrect, please define the correct behavior in this ticket: https://pagure.io/dogtagpki/issue/2838

*** This bug has been marked as a duplicate of bug 1452250 ***


Note You need to log in before you can comment on or make changes to this bug.