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:
FYI. There exists a job plugin that can be enabled to delete expired certs that were published to the publishing directory. You might want to take a look to see if you could massage it into something that will do the same for the intrnaldb.
pki/base/server/cms/src/com/netscape/cms/jobs/UnpublishExpiredJob.java
Per discussions in CS/DS meeting of 02/01/2016: 10.4 major
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
See also IPA ticket for removed expired certs from principal object userCertificate attribute: https://pagure.io/freeipa/issue/7219
userCertificate
Metadata Update from @ftweedal: - Custom field feature adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2307
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)