In the man page of pkispawn for customizing the Certificate System Parameters, it is given that for ocsp signing certificate the tag ocsp_signing should be used in CA and signing in OCSP but also while configuring the certificate parameters for an ocsp subsystem we need to specify ocsp_signing as the tag.
Also,for configuring the private key the parameter pki_keysize is given but the actual parameter as specified in the /etc/pki_default.cfg file is pki_key_size.
Replying to [ticket:1057 saipandi]
Per CS/DS meeting of 06/30/2014, proposed Milestone: Dogtag 10.2.1
Also the tag for ssl server certificate parameters is given as sslserver in the pki_default.cfg man page but it is ssl_server as per the default config file /etc/pki/default.cfg
Proposed Milestone: 10.2.3 (per CS Meeting of 09/17/2014)
man page (complete earlier if possible)
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
("signing") should be ca_signing
Its also not fully apparent what sections all the options should live under in config.txt until you open up /etc/pki/default.cfg and do some digging.
IIRC I had to set pki_audit_signing_subject_dn and pki_admin_subject_dn under specific component sections and not under DEFAULT to get them to do what I expected.
It seems that the initially reported issues are no longer true. if so, I suggest we close this ticket.
dminnich, regarding how clear it is that which parameters go where, I too have to look in /etc/pki/default.cfg. But in general, as pkispawn man pages have have explained, the (potentially) shared parameters are in [DEFAULT] and [TOMCAT] while the subsystem-specific parameters go into each subsystem section. Administrators are per subsystem.
note: those reported issues may one time be the case, but I'm closing the ticket as i do not see any. new tickets can be filed if more issues are found.
Metadata Update from @saipandi: - Issue set to the milestone: 10.2 Backlog
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/1622
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.