Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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

Summary:	Adding serial number into CERT_REQUEST_PROCESSED audit event.
Product:	Red Hat Enterprise Linux 7	Reporter:	Matthew Harmsen <mharmsen>
Component:	pki-core	Assignee:	Endi Sukma Dewata <edewata>
Status:	CLOSED ERRATA	QA Contact:	Asha Akkiangady <aakkiang>
Severity:	unspecified	Docs Contact:	Petr Bokoc <pbokoc>
Priority:	unspecified
Version:	7.4	CC:	akahat, arubin, pbokoc
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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]	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 22:52:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matthew Harmsen 2017-05-18 18:09:53 UTC

This bug is created as a clone of upstream ticket:
https://pagure.io/dogtagpki/issue/2655

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

    [AuditEvent=CERT_REQUEST_PROCESSED]
        [SubjectID=caadmin]
        [Outcome=Success]
        [ReqID=9]
        [CertSerialNum=...]
        [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:

    https://review.gerrithub.io/358704
    https://review.gerrithub.io/358705
    https://review.gerrithub.io/358706

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.

https://access.redhat.com/errata/RHBA-2017:2110