Show Table of Contents
12.4. Using the Certificate System Watchdog Service
In Certificate System, the watchdog service is used to start services which require passwords to access the security database in order to start. In case that there is a requirement not to store the unencrypted passwords on the system, the watchdog service:
- prompts for the relevant passwords during server startup and caches them.
- uses cached passwords in case of a failure when the server is automatically restarted due to a crash.
For further details, see the corresponding section in the Certificate System Planning, Installation, and Deployment Guide.
12.4.1. Enabling the Watchdog Service
To enable the watchdog service:
- Backup the
server.xmlandpassword.conffiles from the/var/lib/pki/instance_name/conf/directory. For example:# cp -p /var/lib/pki/instance_name/conf/server.xml /root/ # cp -p /var/lib/pki/instance_name/conf/password.conf /root/
- Stop and disable the Certificate System instance's service:
# systemctl stop pki-tomcatd@instance_name.service # systemctl disable pki-tomcatd@instance_name.service
- If you use a Hardware Security Module (HSM), enable the watchdog service to prompt for the password of the hardware token:
- Display the name of the hardware token:
# egrep "^hardware-" /var/lib/pki/instance_name/conf/password.conf hardware-HSM_token_name=passwordThe highlighted string in the previous example is the hardware token name. - Add the
cms.tokenListparameter to the/var/lib/pki/instance_name/conf/ca/CS.cfgfile and set it to the name of the hardware token. For example:cms.tokenList=HMS_token_name
- Enable the watchdog configuration for the instance:
# pki-server instance-nuxwdog-enable instance_name
For further details, see the pki-server-nuxwdog(8) man page. - Optionally, to start the instance as the
pkiuseruser instead ofroot:- Copy the watchdog
systemdunit file of the instance to the/etc/systemd/system/directory:# cp -p /usr/lib/systemd/system/instance_name-nuxwdog@.service /etc/systemd/system/
Note
Unit files in the/etc/systemd/system/directory have a higher priority and are not replaced during updates. - Add the following entries to the
[Service]section in the/etc/systemd/system/instance_name-nuxwdog@.servicefile:User=pkiuser Group=pkiuser
- Reload the
systemdconfiguration:# systemctl daemon-reload
- Enable the Certificate System service that uses the watchdog:
# systemctl enable pki-tomcatd-nuxwdog@instance_name.service
- Start the Certificate System instance:
# systemctl start pki-tomcatd-nuxwdog@instance_name.service
12.4.2. Verifying That the Certificate System Watchdog Service is Enabled
To verify that the watchdog service is enabled:
- Verify that the
pki-tomcatd-nuxwdogservice is enabled:# systemctl is-enabled pki-tomcatd-nuxwdog@instance_name.service enabled
- Verify that the
pki-tomcatdservice is disabled:# systemctl is-disabled pki-tomcatd@instance_name.service disabled
- In the
/etc/pki/instance_name/server.xmlfile:- verify that the
passwordFileparameter refers to theCS.cfgfile. For example:passwordFile="/etc/pki/instance_name/ca/CS.cfg"
- verify that the
passwordClassparameter is set tocom.netscape.cms.tomcat.NuxwdogPasswordStore:passwordClass="com.netscape.cms.tomcat.NuxwdogPasswordStore"
12.4.3. Disabling the Watchdog Service
To disable the watchdog service:
- Stop and disable the Certificate System instance's service that uses the watchdog:
# systemctl stop pki-tomcatd-nuxwdog@instance_name.service # systemctl disable pki-tomcatd-nuxwdog@instance_name.service
- Enable the regular service without watch dog for the instance:
# pki-server instance-nuxwdog-disable instance_name
- Disable the watchdog configuration for the instance:
# systemctl enable pki-tomcatd@instance_name.service
For further details, see the pki-server-nuxwdog(8) man page. - Start the Certificate System instance:
# systemctl start pki-tomcatd@instance_name.service

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.