Dogtag 10.2 currently provides the following PKI instance installation/configuration mechanisms:

• 'pkispawn' single-pass installation and configuration (can be run either interactively, or "silently" through a specified configuration file),
• 'pkispawn' (installation only) + 'pkispawn' (configuration only - replaces the 'pkisilent' batch process), or
• 'pkispawn' (installation only) + GUI browser configuration panels for CA, KRA, OCSP, and TKS (there are currently no GUI configuration panels for the revamped TPS) via a Firefox browser; the Firefox browser is the only browser which supports PKI configuration using this interface.

When the 'pkispawn' utility configures a PKI instance, it utilizes the REST interface; however, the GUI browser interface utilizes the original non-REST legacy interface. Both methods eventually utilize the same configuration back-end.

To alleviate many of the design/development/testing/support problems associated with maintaining multiple interfaces, we are planning on removing the GUI browser configuration interface option in Dogtag 10.2 since:

• when run using the single-pass technique, the 'pkispawn' tool can utilize an interactive mode to provide similar functionality and administrator experience,
• the GUI browser configuration panels currently lack support for Dogtag 10.2 instances which may contain more than one type of PKI subsystem (i. e. - it cannot be used to configure a second PKI subsystem within a Dogtag 10.2 instance that already contains a different subsystem - this leads to a failure to configure this second PKI subsystem as well as to the corruption of the original PKI subsystem!),
• we have concerns regarding future Firefox support of some of the features associated with the GUI configuration panels, and
• this should lead to a reduction of required test cases, many of which may have required tedious manual interaction with a tester.

Completion of this ticket requires the following:

(1) remove URL advertisement displayed at the end of a 'pkispawn'
    installation-only mode,
(2) remove all references to the GUI-based configuration option from the man pages,
(3) disable the GUI configuration interface servlet(s)
    in the various 'web.xml' files, and
(4) remove GUI configuration panels as well as any wizard code dedicated to the
    sole purpose of configuring a PKI instance.

proposed Milestones:(1), (2), and (3) - 10.2 (August)
                    (4)               - 10.2.1