Once Dogtag 10: Python 'configuration.py' Configuration Scriptlet is complete, augment it with the ability to generate 'clones' of CA, KRA, OCSP, and TKS subsystems.
Additionally, all "clone" code that calls into the configuration client in the "main()" function of "configuration.jy" has currently been set to the following:
PKI_JYTHON_NOT_YET_IMPLEMENTED
Remember to enable "cloning" once this has been addressed.
RESOLVED FOR "CA" CLONE ONLY:
commit e0a57d039dec42526e5f3241a0439b04f17d4ee5 Author: Matthew Harmsen <mharmsen@redhat.com> Date: Wed Aug 1 21:36:28 2012 -0700
MOVING TICKET FROM "Dogtag 10.0 Alpha" TO "Dogtag 10.0 Beta"
RESOLVED FOR "KRA", "OCSP" and "TKS" CLONES:
commit 0198bf929702b756214b5f509ffe677ca58bf650 Author: Matthew Harmsen <mharmsen@redhat.com> Date: Wed Aug 8 13:41:46 2012 -0700 PKI Deployment Scriptlets * 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
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: Dogtag 10.0.0.a1
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/756
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.