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 1452344 - Adding serial number into CERT_REQUEST_PROCESSED audit event.
Summary: Adding serial number into CERT_REQUEST_PROCESSED audit event.
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
Petr Bokoc
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-18 18:09 UTC by Matthew Harmsen
Modified: 2020-10-04 21:27 UTC (History)
3 users (show)

Fixed In Version: pki-core-10.4.1-5.el7
Doc Type: Bug Fix
Doc Text:
`CERT_REQUEST_PROCESSED` audit log entries now include certificate serial number instead of encoded data Previously, `CERT_REQUEST_PROCESSED` audit log entries included Base64-encoded certificate data. For example: [AuditEvent=CERT_REQUEST_PROCESSED]...[InfoName=certificate][InfoValue=MIIDBD...] This information was not very useful because the certificate data would have to be decoded separately. The code has been changed to include the certificate serial number directly into the log entry, as shown in the following example: [AuditEvent=CERT_REQUEST_PROCESSED]...[CertSerialNum=7]
Clone Of:
Last Closed: 2017-08-01 22:52:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2775 0 None None None 2020-10-04 21:27:21 UTC
Red Hat Product Errata RHBA-2017:2110 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-08-01 19:36:59 UTC

Description Matthew Harmsen 2017-05-18 18:09:53 UTC
This bug is created as a clone of upstream ticket:

The certificate serial number should be added into CERT_REQUEST_PROCESSED audit log as a separate field, for example:

        [InfoName=certificate][InfoValue=MIIDBDCCAey...] certificate request processed

Comment 2 Matthew Harmsen 2017-05-18 18:11:32 UTC
edewata provided the following in the associated Pagure issue:

Patches for review:


This is documented in: http://pki.fedoraproject.org/wiki/CA_Audit_Events.

Comment 4 Amol K 2017-06-13 08:03:34 UTC
I tested this bug on pki 10.4.1-8.el7 build.

It shows the certificate request id and certificate id in the ca_audit logs with the event AuditEvent=CERT_REQUEST_PROCESSED.

verifying this bug.

Comment 5 errata-xmlrpc 2017-08-01 22:52:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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