pki.git/base/deploy/src/scriptlets/pkiparser.py, branch ticket-309

Renamed "shared" folder to "server".

2012-10-08T03:53:23+00:00

The "shared" folder in /usr/share/pki has been renamed
to "server" since it contains only server files.

Ticket #353

add selinux context for pkidaemon, remove unneeded pid and lock code

2012-10-05T19:55:44+00:00

remove runcon from operations, add rules for spawn/destroy,
add mgrepl changes to policy

Fixed conflicting log4j.properties.

2012-09-19T15:36:43+00:00

The /lib link has been replaced with a real folder
which contains links to the files in /usr/share/tomcat/lib. This
way the log4j.properties can be placed in this folder without
causing conflicts with other instances.

Ticket: #284

Added common ROOT webapp.

2012-09-12T17:38:58+00:00

The current ROOT webapp will redirect users coming to the root
URL path to the proper path of the subsystem's webapp.

Since now a single Tomcat instance may have multiple subsystems,
a new ROOT webapp has been added to present the user with a menu
of all available webapps from all subsystems in the instance.

Ticket #89

Added common theme webapp.

2012-09-12T17:38:51+00:00

A new theme webapp has been added to store the theme files for
all PKI webapps. In the future the subsystem webapps can be
modified to use the theme files provided by this common webapp
instead of having to include duplicate files in each webapp.

Ticket #89

Added proxy realm.

2012-09-05T15:09:41+00:00

CMS engine is a singleton and it's used by PKI realm to authenticate
users accessing the subsystem. Since a Tomcat instance may contain
multiple subsystems, each having separate realm, the PKI JAR links
need to be moved into WEB-INF/lib so that they will run inside
separate class loaders.

Tomcat also requires that the authenticator and realm classes be
available in common/lib. To address this a new package pki-tomcat.jar
has been added. The package contains the authenticator and a proxy
realm. When the subsystems start running, they will register their
own realms into the proxy realms such that the authentications will
be forwarded to the appropriate subsystems.

Ticket #89

Moved webapp deployment code into pkispawn.

2012-09-05T15:08:41+00:00

Previously the WAR files were generated at build time, so it would
include theme files that were installed on the build machine.

The code has been changed such that instead of generating WAR files
pkispawn will copy the webapp files from the theme folders and combine
them with subsystem webapp files at deployment time. This way it will
use the actual theme files installed on the deployment machine.

Ticket #89

Verify symbolic links and update CS.cfg for Dogtag 10

2012-08-29T17:08:36+00:00

* TRAC Ticket #301 - Need to modify init scripts to verify needed
  symlinks in an instance
* TRAC Ticket #303 - Dogtag 10: CS.cfg parameters for Dogtag 9 instance
  running under Dogtag 10 packages . . .

PKI Deployment Scriptlets

2012-08-17T22:07:19+00:00

* TRAC Ticket #266 - for non-master CA subsystems, pkidestroy needs to
  contact the security domain to update the domain
* Made Fedora 17 rely upon tomcatjss 7.0.0 or later
* Changed Dogtag 10 build-time and runtime requirements for 'pki-deploy'
* Altered PKI Package Dependency Chain (top-to-bottom):
  pki-ca, pki-kra, pki-ocsp, pki-tks --> pki-deploy --> pki-common
* Changed TPS to require a build-time dependency of 'httpd-devel >= 2.4.2'
* Clarified RPM build script's usage message

PKI Deployment Scriptlets

2012-08-13T15:39:47+00:00

* TRAC Ticket #184 - Dogtag 10: Update PKI Deployment to handle
  cloning CA/KRA/OCSP/TKS . . .
* TRAC Ticket #285 - Dogtag 10: Fix installation issues for
  KRA, OCSP, and TKS