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.

This bug is created as a clone of upstream ticket:

https://pagure.io/dogtagpki/issue/1750

Currently there is no automatic mechanism to purge expired certificates and the corresponding request objects from the database, so over time the database can grow very large.

There should be an automatic mechanism to purge expired certificates which can be optionally enabled based on certain policies, for example:

database size limit
number of expired certificates
time elapsed since expiration date

Upstream PKI issue is now: https://github.com/dogtagpki/pki/issues/2307

Moving to Dogtag. As noted in the IPA upstream ticket:

I do not think we should prune these directly from Dogtag's DB.
Dogtag should have an interface to let IPA do it (if necessary).
There could even be rules configured on Dogtag side that keep some certificates, for instance those that expired within the past year as asked by the reporter.

Implemented in master branch (PKI 11.3):
* https://github.com/dogtagpki/pki/commit/9e9b303327dd794d727ccb1e3649511e99413747
* https://github.com/dogtagpki/pki/commit/1d2410da32d505b6cfcd5bbbe3ac9cce1163859b

Docs:
* https://github.com/dogtagpki/pki/wiki/CA-Database-Pruning
* https://github.com/dogtagpki/pki/wiki/Configuring-CA-Database-Pruning

Fedora COPR build: https://copr.fedorainfracloud.org/coprs/g/pki/master/builds/

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 (Moderate: pki-core security, 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/RHSA-2023:2293

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days