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.
Build used for verification:
root@csqa4-guest01 ~ # rpm -qi pki-base
Name : pki-base
Version : 10.5.1
Release : 8.el7
Architecture: noarch
Install Date: Wednesday 14 February 2018 11:38:05 PM EST
Group : System Environment/Base
Size : 2120548
License : GPLv2
Signature : RSA/SHA256, Monday 12 February 2018 09:55:01 PM EST, Key ID 199e2f91fd431d51
Source RPM : pki-core-10.5.1-8.el7.src.rpm
Build Date : Monday 12 February 2018 09:19:29 PM EST
Build Host : ppc-035.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor : Red Hat, Inc.
URL : http://pki.fedoraproject.org/
Summary : Certificate System - PKI Framework
Description :
The PKI Framework contains the common and client libraries and utilities
written in Python. This package is a part of the PKI Core used by the
Certificate System.
Steps followed for verification
1. Generate a certificate request
2. Reject a certificate request
3. Cancel a certificate request
Observations:
1. Certificate request is successfully submitted to CA
2. On Rejecting a certificate request the following log event is generated
0.http-bio-8443-exec-10 - [15/Feb/2018:00:34:32 EST] [14] [6] [AuditEvent=CERT_REQUEST_PROCESSED][SubjectID=caadmin][Outcome=Failure][ReqID=20][InfoName=rejectReason][InfoValue=<null>] certificate request processed
3. On Cancelling a certificate request the following log event is generated
0.http-bio-8443-exec-10 - [15/Feb/2018:00:35:25 EST] [14] [6] [AuditEvent=CERT_REQUEST_PROCESSED][SubjectID=caadmin][Outcome=Failure][ReqID=19][InfoName=cancelReason][InfoValue=<null>] certificate request processed
I am attaching the logs for the same.
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-2018:0925
The following CERT_REQUEST_PROCESSED events seem to have incorrect outcomes. These successes probably should have been failures: https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1090 https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1148 These failures probably should have been successes: https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L467 https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1255 https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1298 https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1342 https://github.com/dogtagpki/pki/blob/0f3e03ee3ee0afb3044f61ce1d091493ed76eded/base/server/cms/src/com/netscape/cms/servlet/request/ProcessCertReq.java#L1386 Per discussion with cfu and alee, the CERT_REQUEST_PROCESSED's outcome can be interpreted in two ways: Success means that the request has been processed, but the certificate may or may not be issued, depending on approval or rejection. Failure means that there is a problem so the request cannot be processed. Success means the request is approved so the certificate is issued. Failure means that the certificate is not issued due to rejection or other problems. The definition of the outcome needs to be clarified first, then the code needs to be fixed accordingly. See also: Bugzilla Bug #1452250 - Inconsistent CERT_REQUEST_PROCESSED event in ConnectorServlet.