The Dogtag Certificate System is an enterprise-class Certificate Authority (CA) which supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management.
This issue was migrated from Pagure Issue #1564. Originally filed by edewata (@edewata) on 2015-08-15 02:40:27:
Assigned to nobody
Currently a number of LDIF files are stored in the following folders:
/usr/share/pki/server/conf/
/usr/share/pki//conf/
and they are deployed into the instance folder (except for some files explicitly excluded from deployment).
Most (if not all) of these LDIF files are templates or static files that can actually be used without changing the file itself, so they don't actually need to be deployed into the instance folder, or they do not need to be kept in the instance folder after installation. This will reduce the number of files in the instance folder.
Proposed solution:
Move the LDIF files to separate LDIF folders (e.g. /usr/share/pki/server/ldif/ and /usr/share/pki//ldif/) so they don't get deployed.
For template LDIF files, customize the file in memory or into a temporary file, then remove the temporary file after usage.
For static LDIF files, use the file directly from the new LDIF folder.
This issue was migrated from Pagure Issue #1564. Originally filed by edewata (@edewata) on 2015-08-15 02:40:27:
Currently a number of LDIF files are stored in the following folders:
and they are deployed into the instance folder (except for some files explicitly excluded from deployment).
Most (if not all) of these LDIF files are templates or static files that can actually be used without changing the file itself, so they don't actually need to be deployed into the instance folder, or they do not need to be kept in the instance folder after installation. This will reduce the number of files in the instance folder.
Proposed solution: