Ade wrote:
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
@edewata
For 1, we have the pki-server selftest-enable and pki-server selftest-disable options.
pki-server selftest-enable
pki-server selftest-disable
2 isn't clear
3 is no longer required since we have deprecated console.
If this has been addressed, can we close this ticket?
Metadata Update from @dmoluguw: - Custom field feature adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None
Here are the selftest properties in CS.cfg:
selftests._000=## selftests._001=## Self Tests selftests._002=## selftests._003=## The Self-Test plugin SystemCertsVerification uses the selftests._004=## following parameters (where certusage is optional): selftests._005=## ca.cert.list = <list of cert tag names deliminated by ","> selftests._006=## ca.cert.<cert tag name>.nickname selftests._007=## ca.cert.<cert tag name>.certusage selftests._008=## selftests.container.instance.CAPresence=com.netscape.cms.selftests.ca.CAPresence selftests.container.instance.CAValidity=com.netscape.cms.selftests.ca.CAValidity selftests.container.instance.SystemCertsVerification=com.netscape.cms.selftests.common.SystemCertsVerification selftests.container.logger.bufferSize=512 selftests.container.logger.class=com.netscape.cms.logging.RollingLogFile selftests.container.logger.enable=true selftests.container.logger.expirationTime=0 selftests.container.logger.fileName=[PKI_INSTANCE_PATH]/logs/[PKI_SUBSYSTEM_TYPE]/selftests.log selftests.container.logger.flushInterval=5 selftests.container.logger.level=1 selftests.container.logger.maxFileSize=2000 selftests.container.logger.register=false selftests.container.logger.rolloverInterval=2592000 selftests.container.logger.type=transaction selftests.container.order.onDemand=CAPresence:critical, SystemCertsVerification:critical, CAValidity:critical selftests.container.order.startup=CAPresence:critical, SystemCertsVerification:critical selftests.plugin.CAPresence.CaSubId=ca selftests.plugin.CAValidity.CaSubId=ca selftests.plugin.SystemCertsVerification.SubId=ca
Currently we have pki-server <subsystem>-config commands to edit any property in CS.cfg which satisfy #1, and we have pki-server selftest-enable/disable commands which satisfy #2 (ideally they should be moved into pki-server <subsystem>-selftest).
pki-server <subsystem>-config
pki-server selftest-enable/disable
pki-server <subsystem>-selftest
I agree that #3 is not required. Selftests should run before the server is running (or at least as soon as the server is running). I don't think it makes sense to rerun them after the server is running for a while (e.g. what do we do if selftest fails, shutdown the server?), but we do have interface in PKI console and pki <subsystem>-selftest commands for that. Request #3 was referring to the PKI console part. Since we already have a plan for the health check tool, this should no longer be needed. We may also deprecate the pki <subsystem>-selftest commands as well.
pki <subsystem>-selftest
I'm closing the ticket. Thanks!
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
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/1323
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.