pki.git/base/deploy/src/scriptlets/pkiconfig.py, branch ticket-501

Added interactive subsystem installation.

2013-02-04T23:48:02+00:00

The pkispawn has been modified such that the configuration file
and subsystem type are optional. The pkidestroy has been modified
such that the instance name and subsystem type are optional.
If any of these options are not specified they will enter an
interactive mode.

Ticket #380

interpolate more paths

2012-12-19T02:38:12+00:00

Parameterizing RESTEasy paths.

2012-12-07T02:23:11+00:00

The paths to RESTEasy jar files have been modified such that it can
be configured globally at build time using the spec file to support
different distributions, and at deployment time using a system-wide
configuration in /etc/pki/pki.conf.

Ticket #422, #423.

Archiving default deployment configuration.

2012-12-04T20:50:55+00:00

The default deployment configuration has been renamed and moved to
/etc/pki/default.cfg to make it more accessible to users. The pkispawn
has been modified to archive the default deployment configuration
along with the user-provided configuration in the registry. The
pkidestroy will now use both archived configuration files to ensure
proper removal of the subsystem.

Ticket #399

Use interpolation to build default parameters

2012-12-04T17:11:36+00:00

This patch replaces the code in pkiparser with defaults that are
built up using ConfigParser interpolation.  The patch gets most
(but not all) default parameters.

Simplified the configuration file using defaults.

2012-11-30T21:03:07+00:00

Previously to create a subsystem the admin would have to copy the
entire default deployment configuration, which contains many
parameters, and then customize it. Now the deployment code has been
changed such that the default config file will be used to provide
the default values, so the admin will only need to provide the
non-default parameters, thus reducing the size of the file.

Sample configuration files are provided in /usr/share/pki/
deployment/config.

Ticket #399

Reorganized sensitive parameters.

2012-11-30T21:02:48+00:00

Previously sensitive parameters are stored in the Sensitive section in
the configuration file, separate from the hierarchical structure used
by non-sensitive parameters. To allow defining multiple subsystems in
a single configuration file the sensitive and non-sensitive parameters
have been reorganized into the same hierarchical structure.

To maintain the security a new meta-parameter has been added to list
all sensitive parameter names. This way the deployment code will know
whether a parameter is sensitive, which then will mask the value before
displaying it to the screen or storing it in a log file.

Ticket #399

Link to resteasy-base on rhel systems when running pkispawn

2012-11-21T05:04:32+00:00

removed dry_run from pkispawn

2012-11-11T04:10:15+00:00

Ticket 411

Enable Subordinate CA

2012-11-08T17:57:21+00:00

* TRAC Ticket #185 - Dogtag 10: Update PKI Deployment to handle subordinate CA