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.
Description of problem:
When the CA attempts to build a CRL a search is performed that is different from previous versions and is now performing an unindexed search. With a rather large database, this will cause the CRL to not generate as it will timeout before completion.
Version-Release number of selected component (if applicable):
pki-ca-10.5.16-6.el7_7.noarch
This appears to affect all the 10.x line.
How reproducible:
Very
Steps to Reproduce:
1. Build generic CA
2. Start CA
3. It auto-generates a CRL on startup.
Actual results:
/var/log/dirsrv/slapd-rhcs/access
02/Mar/2020:12:35:39.413266718 -0500] conn=40 op=11 SRCH base="ou=certificateRepository,ou=ca,o=pki-tomcat-CA" scope=1 filter="(&(certStatus=REVOKED)(|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain)))" attrs="serialno revInfo objectClass"
[02/Mar/2020:12:35:39.413454492 -0500] conn=40 op=11 SORT serialno (0)
[02/Mar/2020:12:35:39.413464335 -0500] conn=40 op=11 VLV 0:100:A 0:0 (0)
[02/Mar/2020:12:35:39.413491873 -0500] conn=40 op=11 RESULT err=0 tag=101 nentries=0 etime=0.0000300364 notes=U
The new search now includes the filter of ' (|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain) '.
Expected results:
02/Mar/2020:12:35:39.413266718 -0500] conn=40 op=11 SRCH base="ou=certificateRepository,ou=ca,o=pki-tomcat-CA" scope=1 filter="(&(certStatus=REVOKED))" attrs="serialno revInfo objectClass"
[02/Mar/2020:12:35:39.413454492 -0500] conn=40 op=11 SORT serialno (0)
[02/Mar/2020:12:35:39.413464335 -0500] conn=40 op=11 VLV 0:100:A 0:0 (0)
[02/Mar/2020:12:35:39.413491873 -0500] conn=40 op=11 RESULT err=0 tag=101 nentries=0 etime=0.0000300364
This is what the old search would filter.
Additional info:
The fix we performed was to create a new vlv index to include the above data. It would be good to know if this change was intended or not. Also, updating the vlv.ldif with the new index should be be intended.
dn: cn=allRevokedCaCertsCRL-{instanceId}, cn={database}, cn=ldbm database, cn=plugins, cn=config
objectClass: top
objectClass: vlvSearch
cn: allRevokedCaCertsCRL-{instanceId}
vlvBase: ou=certificateRepository,ou=ca,{rootSuffix}
vlvScope: 1
vlvFilter: (&(certStatus=REVOKED)(|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain)))
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 (pki-core bug fix and enhancement update), 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-2020:3941
Description of problem: When the CA attempts to build a CRL a search is performed that is different from previous versions and is now performing an unindexed search. With a rather large database, this will cause the CRL to not generate as it will timeout before completion. Version-Release number of selected component (if applicable): pki-ca-10.5.16-6.el7_7.noarch This appears to affect all the 10.x line. How reproducible: Very Steps to Reproduce: 1. Build generic CA 2. Start CA 3. It auto-generates a CRL on startup. Actual results: /var/log/dirsrv/slapd-rhcs/access 02/Mar/2020:12:35:39.413266718 -0500] conn=40 op=11 SRCH base="ou=certificateRepository,ou=ca,o=pki-tomcat-CA" scope=1 filter="(&(certStatus=REVOKED)(|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain)))" attrs="serialno revInfo objectClass" [02/Mar/2020:12:35:39.413454492 -0500] conn=40 op=11 SORT serialno (0) [02/Mar/2020:12:35:39.413464335 -0500] conn=40 op=11 VLV 0:100:A 0:0 (0) [02/Mar/2020:12:35:39.413491873 -0500] conn=40 op=11 RESULT err=0 tag=101 nentries=0 etime=0.0000300364 notes=U The new search now includes the filter of ' (|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain) '. Expected results: 02/Mar/2020:12:35:39.413266718 -0500] conn=40 op=11 SRCH base="ou=certificateRepository,ou=ca,o=pki-tomcat-CA" scope=1 filter="(&(certStatus=REVOKED))" attrs="serialno revInfo objectClass" [02/Mar/2020:12:35:39.413454492 -0500] conn=40 op=11 SORT serialno (0) [02/Mar/2020:12:35:39.413464335 -0500] conn=40 op=11 VLV 0:100:A 0:0 (0) [02/Mar/2020:12:35:39.413491873 -0500] conn=40 op=11 RESULT err=0 tag=101 nentries=0 etime=0.0000300364 This is what the old search would filter. Additional info: The fix we performed was to create a new vlv index to include the above data. It would be good to know if this change was intended or not. Also, updating the vlv.ldif with the new index should be be intended. dn: cn=allRevokedCaCertsCRL-{instanceId}, cn={database}, cn=ldbm database, cn=plugins, cn=config objectClass: top objectClass: vlvSearch cn: allRevokedCaCertsCRL-{instanceId} vlvBase: ou=certificateRepository,ou=ca,{rootSuffix} vlvScope: 1 vlvFilter: (&(certStatus=REVOKED)(|(!(issuerName=*))(issuerName=CN=CA Signing Certificate,OU=pki-tomcat,O=example Security Domain)))