<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> 1. I don't think we should assume that the installer is root. I suggest you change the following line from setup the path where the admin certificate of this <subsystem> should be stored. The default value is /root/.dogtag/pki-tomcat/<ca/kra/ocsp/tks/tps>_admin.cert. to something like setup the path where the admin certificate of this <subsystem> should be stored. The default value is $HOME/.dogtag/pki-tomcat/<ca/kra/ocsp/tks/tps>_admin.cert. If there are other places like this in this man pages or any other documentation, we should make sure we do this correct.y 2. I do not find any mentioning of the need to set up the shared secret between TKS and TPS after pkispawn if one were to install TKS and TPS on separate tomcat instances. Please add that as a note and point to wherever the detail is at(possibly another tps-specific man page). Can also mention that in the case of shared tomcat instance, pkispawn takes cared of it. 3. probably no action needed from you now, but I need to write a man page for TPS externalReg feature. We can discuss more on irc if needed. thanks, Christina <div class="moz-cite-prefix">On 07/17/2015 08:09 AM, Endi Sukma Dewata wrote: </div> <blockquote cite="mid:55A91AA5.90809@redhat.com" type="cite">The man pages for pkispawn and pki_default.cfg have been updated to include TPS deployment parameters. <a class="moz-txt-link-freetext" href="https://fedorahosted.org/pki/ticket/1277">https://fedorahosted.org/pki/ticket/1277</a> <fieldset class="mimeAttachmentHeader"></fieldset> <pre wrap="">_______________________________________________ Pki-devel mailing list <a class="moz-txt-link-abbreviated" href="mailto:Pki-devel@redhat.com">Pki-devel@redhat.com</a> <a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pki-devel">https://www.redhat.com/mailman/listinfo/pki-devel</a></pre> </blockquote> </body> </html>