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

Resolved Trac Ticket 367 - pkidestroy does not remove connector

2013-01-15T14:28:38+00:00

* Added RESTful servlet to add/remove a KRA connector from the CA.
* Modified ACL to allow KRA subsystem user to remove connector.
* Modified connector code to allow the connector to be replaced without a server restart.
* Added functionality to pki CLI to add/remove connector
* Added code to pkidestroy to remove the connector (using both pki CLI and sslget)
  When the issues with pki connection are resolved, we will use that method instead.
* Modified sslget to accept HTTP return codes != 200.  In this case, we were returning
  204 - which is perfectly legitimate.

pkispawn modified to not relabel when selinux is disabled

2012-12-19T05:05:38+00:00

Ticket 393

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.

Implemented ability to utilize an external CA

2012-12-06T22:41:28+00:00

* TRAC Ticket #231 - Dogtag 10: Update PKI Deployment to handle external CA

Interpolation correction patch based on review comments

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

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

Enable Subordinate CA

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

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

Convert admin cert from ascii to binary before importing into certdb

2012-11-05T03:13:21+00:00

Sometimes importing the ascii admin cert into th client certdb fails.
The binary always appears to work though.

Allow a PKI instance to be installed/configured independently

2012-10-30T14:56:06+00:00

* TRAC Ticket #286 - Dogtag 10: Create parameter for optionally allowing
  a user to skip configuration . . .