Per comments from alee@redhat.com on the PKI Deployment Framework PKI Trac Issues patch dated (07/28/2012):
* Fix the incorrect test for an empty 'pki_token_name' * Remove the 'pki_client_pkcs12_path' parameter from 'pkideployment.cfg', and ALWAYS store the PKI client Admin Cert PKCS #12 file under the NSS "server" security database directory * Simplify the code that calculates the name of 'pki_client_admin_cert' and the path of 'pki_client_admin_cert_p12' * Remove the 'pki_backup_file' parameter from 'pkideployment.cfg', and ALWAYS store the PKI Backup Keys PKCS #12 file under the NSS "server" security database directory * Simplify the code that calculates the path of 'pki_backup_keys_p12' (formerly called 'pki_backup_file') * Fix the 'pkideployment.cfg' file (and associated code) such that: * names ending with 'path' are ONLY used to specify complete directory paths to a filename that always end by specifying that filename * names ending with 'dir' are ONLY used to specify directories * names ending with 'file' are ONLY used to specify the name of a file * names ending with 'name' are ONLY used to specify strings that do not refer to either a directory or a file * Refactor code to allow the "pkideployment.cfg" file utilized by pkispawn to be stored as soon as possible in the "infrastructure_layout" scriptlet (rather than the "instance_layout", "subsystem_layout", and "finalization" scriptlets) * Change the 'directory', 'file', and 'symlink' classes' delete() method to issue a warning for a non-existent directory, file, or symlink respectively rather than terminating the process with an error * Fix the [PKI_OPEN_AJP_PORT_COMMENT_SLOT], [PKI_CLOSE_AJP_PORT_COMMENT_SLOT], [PKI_OPEN_ENABLE_PROXY_COMMENT_SLOT], and [PKI_CLOSE_ENABLE_PROXY_COMMENT_SLOT] to depend upon the boolean value of 'pki_enable_proxy'
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/849
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.
Login to comment on this ticket.