Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAsha Akkiangady
2017-06-19 04:00:56 UTC
Created attachment 1288990[details]
Manually enabling nuxwdog for CA throws incorrect password exception
Description of problem:
Manually enabling nuxwdog throws incorrect password exception.
Version-Release number of selected component (if applicable):
How reproducible:
nuxwdog-1.0.3-5.el7.x86_64
pki-ca-10.4.1-9.el7.noarch
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] Please provide the password for internaldb: ************
[pki-master] Please provide the password for internaldb: *********
[pki-master] Please provide the password for replicationdb: *********
# cat /var/lib/pki/pki-master/conf/password.conf
internal=pS"1V+nx}0Ns
internaldb=Secret123
replicationdb=211285502
Actual results:
Incorrect password exception is thrown. CA debug log attached.
Expected results:
CA should start successfully.
Additional info: