General Availability of CS/IPA Implementation for Separating Default PKI Instance Creation from PKI Subsystem Packaging

‘’’NOTE:

While porting Dogtag from using tomcat5 (Dogtag 1.3) to tomcat6 (Dogtag 9.0), numerous changes were made to the registry model defined below. These changes are discussed in Bugzilla Bug #632425 - Port to tomcat6.

The changes documented in the following bugs have been successfully checked into the source code on the CS/IPA TIP of the Dogtag Subversion Repository:

• Bugzilla Bug #529070 - rpm packaging problems (cannot reinstall correctly)

• Bugzilla Bug #547471 - Apply PKI SELinux changes to PKI registry model

• Bugzilla Bug #553072 - Apply “registry” logic to pki-kra . . .

• Bugzilla Bug #553074 - Apply “registry” logic to pki-ocsp . . .

• Bugzilla Bug #553075 - Apply “registry” logic to pki-tks . . .

• Bugzilla Bug #553076 - Apply “registry” logic to pki-ra . . .

• Bugzilla Bug #553078 - Apply “registry” logic to pki-tps . . .

These will be made available for the following Dogtag Certificate System subsystems once Dogtag Certificate System 1.3.0 is released:

• Certificate Authority (CA) - (pki-ca)

• Data Recovery Manager (DRM) - (pki-kra)

• Online Certificate Status Protocol (OCSP) Manager - (pki-ocsp)

• Token Key Service (TKS) - (pki-tks)

• Registration Authority (RA) - (pki-ra)

• Token Processing System (TPS) - (pki-tps)