Manually enabling nuxwdog throws incorrect password exception.
Steps to Reproduce:
1. pkispawn a CA instance with internal token. 2. Followed manual process instructions from http://pki.fedoraproject.org/wiki/Nuxwdog The manual procedure did not work, CA server failed to start. I noticed a difference between the manual process instruction to enable nuxwdog and the simple process using pki-server nuxwdog enable: Manual process asked to create /var/lib/pki/pki-master/conf/nuxwdog.conf like this: ExeFile /usr/share/java-utils/java-wrapper ExeArgs /usr/share/java-utils/java-wrapper \ -DRESTEASY_LIB=/usr/share/java/resteasy \ -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/lib/java/commons-daemon.jar \ -Dcatalina.base=/var/lib/pki/pki-master \ -Dcatalina.home=/usr/share/tomcat \ -Djava.endorsed.dirs= \ -Djava.io.tmpdir=/var/lib/pki/pki-master/temp \ -Djava.util.logging.config.file=/var/lib/pki/pki-master/conf/logging.properties \ -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \ -Djava.security.manager \ -Djava.security.policy==/var/lib/pki/pki-master/conf/catalina.policy \ org.apache.catalina.startup.Bootstrap start TmpDir /var/lib/pki/pki-master/logs/pids ChildSecurity 1 ExeOut /var/lib/pki/pki-master/logs/catalina.out ExeErr /var/lib/pki/pki-master/logs/catalina.out ExeBackground 1 PidFile /var/lib/pki/pki-master/logs/wd-pki-master.pid ChildPidFile /var/lib/pki/pki-master/logs/pki-master.pid Simple process created /var/lib/pki/pki-master/conf/nuxwdog.conf file with following content: ExeFile /usr/lib/jvm/jre-1.8.0-openjdk/bin/java ExeArgs /usr/lib/jvm/jre-1.8.0-openjdk/bin/java -DRESTEASY_LIB=/usr/share/java/resteasy-base -Djava.library.path=/usr/lib64/nuxwdog-jni -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/var/lib/pki/pki-master -Dcatalina.home=/usr/share/tomcat -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/lib/pki/pki-master/temp -Djava.util.logging.config.file=/var/lib/pki/pki-master/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start TmpDir /var/lib/pki/pki-master/logs/pids ChildSecurity 1 ExeOut /var/lib/pki/pki-master/logs/catalina.out ExeErr /var/lib/pki/pki-master/logs/catalina.out ExeBackground 1 PidFile /var/lib/pki/pki-master/logs/wd-pki-master.pid ChildPidFile /var/lib/pki/pki-master/logs/pki-master.pid 3. For the manual process I created file /var/lib/pki/pki-master/conf/nuxwdog.conf with the content same as from simple process; now CA start is proceeding and asking for passwords, # systemctl start pki-tomcatd-nuxwdog@pki-master.service [pki-master] Please provide the password for internaldb: ************ [pki-master] Please provide the password for internaldb: ********* [pki-master] Please provide the password for replicationdb: *********
Actual results
Incorrect password exception is thrown. CA debug log attached.
Expected results:
CA should start successfully.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1462599 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue assigned to vakwetu
Ade Lee 2017-08-10 16:39:47 EDT
Wiki page updated with current info. (i.e. - replaced the nuxwdog.conf contents).
Metadata Update from @mharmsen: - Issue close_status updated to: invalid - Issue set to the milestone: 10.4.10 (was: 10.4) - 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/2870
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.