dogtagpki

#601 GUI-based vs. REST-based installation/configuration parameters
Closed: Invalid Opened by mharmsen.

Closed: Invalid
Reopen Issue

When using the 'pkispawn' non-interactive mode, certain mandatory parameters are checked to be certain that they are defined. Currently, these decisions are based upon the user performing the REST-based configuration.

However, if the user specifies 'pki_skip_configuration=True', then not all of these parameters are necessarily mandatory, and as per GUI-based configuration may not work with combined instance, there may be other parameters that should be mandatory such as an instance name and ports being different from those defined for an existing instance.

[06/04/2014] - Moving to Milestone 10.2.3 due to schedule restrictions.

Resolving as WONTFIX since the legacy GUI-based configuration will no longer be supported.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.2.3

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

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
None
None
None
None
Normal
defect
Installation/Configuration
Installer Cleanup/ Improvement
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.