Currently the pkispawn man page provides examples with some parameters defined in [DEFAULT] section, e.g:
[DEFAULT] pki_admin_password=Secret123 pki_client_pkcs12_password=Secret123 pki_ds_password=Secret123
These parameters should have been defined in [<subsystem>] section since they are subsystem-specific, i.e.:
[CA] pki_admin_password=Secret123 pki_client_pkcs12_password=Secret123 pki_ds_password=Secret123
The man page should be updated and pkispawn should generate warnings if these parameters are defined in [DEFAULT] section in the user configuration file.
Note that the location of the parameters in the default.cfg is irrelevant. They could be moved into [<subsystem>] as well, or they can stay in [DEFAULT] for other reasons (e.g. backward compatibility).
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @vakwetu: - Issue priority set to: major - Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)
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/2933
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)
Login to comment on this ticket.