By default, 'pkispawn' generates a random pin, an NSS client security database, and a PKCS #12 file containing the Admin Certificate under "/tmp/{pki_instance_id}_client/. This temporary directory remains around (and is eventually removed by 'pkidestroy').
It has been suggested to:
(1) Generate the entire "/tmp/{pki_instance_id}_client/" directory as is, (2) Move the final PKCS #12 file containing the Admin Certificate to some default location (e. g. - /var/lib/pki/{pki_instance_id}/alias) configurable via an optional 'pkideployment.cfg' parameter called "pki_client_pkcs12_path" initialially configured as "pki_client_pkcs12_path=" (unset) (3) Destroy the entire "/tmp/{pki_instance_id}_client/" directory structure unless the optional 'pkideployment.cfg' parameter called "pki_client_database_purge" has been set to "False" (by default it will be set to "pki_client_databse_purge=True"
'pkidestroy' can be changed to:
(1) ignore the client area (which more than often will not be there), or (2) continue to always attempt to remove this area NOTE: It cannot "honor" the value of the configuration file parameter because 'pkidestroy' utilizes a copy of the original "configuration" file that it was provided during 'pkispawn' installation.
Based on conversation with Rob:
We also want the following for IPA installation: 1. ability to specify the location of the client cert stuff, with it defaulting to /tmp/{instance}_client 2. ability to specify the password of the client cert db
Resolved:
commit f589cc1e267d6d7b67a6463b4495b7a9c982669f Author: Matthew Harmsen <mharmsen@redhat.com> Date: Sat Jul 28 18:59:30 2012 -0700
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: Dogtag 10.0 Alpha
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/836
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.