dogtagpki

#518 Remove UI dependencies from pkispawn . . .
Closed: Fixed Opened by mharmsen.

Closed: Fixed
Reopen Issue

This ticket is related to the following bug:

  • Bugzilla Bug #916134 - unresolved dependency in pki-server: pki-server-theme

In attempting to fix this by simply removing the 'pki-server-theme' runtime
dependency from the spec file, it was discovered that 'pkispawn' still always
copied the UI contents from '/usr/share/pki/common-ui' to an instance.

From the spawn() method of 'webapp_deployment.py':

            # Copy /usr/share/pki/common-ui
            # to <instance>/webapps/pki
            util.directory.create(master['pki_tomcat_webapps_common_path'])
            util.directory.copy(
                os.path.join(
                    config.PKI_DEPLOYMENT_SOURCE_ROOT,
                    "common-ui"),
                master['pki_tomcat_webapps_common_path'],
                overwrite_flag=True)

At a bare minimum, this code needs to be run "optionally" since we will no longer specifically require a 'theme'.

However, a more complete fix might allow the user
to specify a specific theme for a specific subsystem within an instance, and allow
pkispawn to copy the appropriate UI to the appropriate place(s).

Additionally, the 'pki-server-theme' runtime dependency should be removed from the
'pki-core.spec' file, and the following comment:

Finally, for deployment purposes, Certificate System requires ONE AND  \
ONLY ONE of the following "Mutually-Exclusive" PKI Theme packages:     \
                                                                       \
  * dogtag-pki-theme (Dogtag Certificate System deployments)           \
  * ipa-pki-theme    (IPA deployments)                                 \
  * redhat-pki-theme (Red Hat Certificate System deployments)          \
                                                                       \

should be changed to:

Finally, if Certificate System is being deployed as an individual or   \
set of standalone rather than embedded server(s)/service(s), it is     \
strongly recommended (though not explicitly required) to include at    \
least one PKI Theme package:                                           \
                                                                       \
  * dogtag-pki-theme (Dogtag Certificate System deployments)           \
    * dogtag-pki-server-theme                                          \
    * dogtag-pki-console-theme                                         \
  * redhat-pki-server-theme (Red Hat Certificate System deployments)   \
    * redhat-pki-server-theme                                          \
    * redhat-pki-console-theme                                         \
  * customized pki theme (Customized Certificate System deployments)   \
    * <customized>-pki-server-theme                                    \
    * <customized>-pki-console-theme                                   \
                                                                       \
  NOTE:  As a convenience for standalone deployments, top-level meta   \
         packages may be provided which bind a particular theme to     \
         these certificate server packages.                            \
                                                                       \

Similarly, the 'pki-ra-theme' runtime dependency should be removed from the 'pki-ra.spec'
file, and the 'pki-tps-theme' runtime dependency should be removed from the 'pki-tps.spec'
file, and the following comment in each file:

Additionally, Certificate System requires ONE AND ONLY ONE of the         \
following "Mutually-Exclusive" PKI Theme packages:                        \
                                                                          \
  * dogtag-pki-theme (Dogtag Certificate System deployments)              \
  * redhat-pki-theme (Red Hat Certificate System deployments)             \
                                                                          \

should be changed to:

Additionally, if Certificate System is being deployed as an individual \
or set of standalone rather than embedded server(s)/service(s), it is  \
strongly recommended (though not explicitly required) to include at    \
least one PKI Theme package:                                           \
                                                                       \
  * dogtag-pki-theme (Dogtag Certificate System deployments)           \
    * dogtag-pki-server-theme                                          \
    * dogtag-pki-console-theme                                         \
  * redhat-pki-server-theme (Red Hat Certificate System deployments)   \
    * redhat-pki-server-theme                                          \
    * redhat-pki-console-theme                                         \
  * customized pki theme (Customized Certificate System deployments)   \
    * <customized>-pki-server-theme                                    \
    * <customized>-pki-console-theme                                   \
                                                                       \
  NOTE:  As a convenience for standalone deployments, top-level meta   \
         packages may be provided which bind a particular theme to     \
         these certificate server packages.                            \
                                                                       \

Checked into master:

  • cead7472df922841bd6648cc82f917351b3c1648

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.0.2

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1088

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Normal
defect
Installation/Configuration
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.