#2930 Verify validity of parameters in user-defined pkispawn override files
Closed: migrated 4 years ago by dmoluguw. Opened 7 years ago by mharmsen.

When pkispawn is invoked with a user-defined override file (specified by the -f <config_file> command-line option), it may be helpful to add code which would validate that each and every "override" parameter specified by the user exists in the default /etc/pki/default.cfg file.

For example, a common mistake may be as simple as a "typo" in the user-defined override file which may produce unintended consequences since the user-defined value would not be applied to the parameter intended to be overridden.


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/3048

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

4 years ago

Log in to comment on this ticket.

Metadata