#1455 pkispawn CA with SSL enabled directory server instance fails
Closed: Invalid Opened by rpattath.

pkispawn CA with SSL enabled directory server instance fails

Steps to Reproduce:

1. setup-ds.pl - instance-name=pki-ca-ldap, baseDN=dc=pki-ca
2. Run setupssl2.sh as follows
# /path/to/setupssl2.sh /etc/dirsrv/slapd-pki-ca-ldap 389 636
DIRECTORY_MANAGER_PASSWORD
3. cd /etc/dirsrv/slapd-pki-ca-ldap
4. /usr/lib64/mozldap/ldapsearch -Z -h localhost -p 636 -D "cn=Directory
Manager" -w Secret123 -b "dc=pki-ca" "objectclass=*" is successful
5. certutil -L -d /etc/dirsrv/slapd-pki-ca-ldap -n "CA certificate" -a >
/root/ca_cert.pem
6. pkispawn CA using the inf in the attachment
https://bugzilla.redhat.com/attachment.cgi?id=1044869

Actual results:

[root@mgmt3 slapd-pki-ca-ldap]# pkispawn -s CA -f /tmp/ca_instance_man.inf
Log file: /var/log/pki/pki-ca-spawn.20150630232927.log
Loading deployment configuration from /tmp/ca_instance_man.inf.
Installing CA into /var/lib/pki/pki-master.
Storing deployment configuration into
/etc/sysconfig/pki/tomcat/pki-master/ca/deployment.cfg.
pkispawn    : ERROR    ....... Exception from Java Configuration Servlet: 500
Server Error: Internal Server Error
pkispawn    : ERROR    ....... ParseError: not well-formed (invalid token):
line 1, column 0: {"Attributes":{"Attribute":[]},"ClassName":"com.netscape.cert
srv.base.PKIException","Code":500,"Message":"Error in populating database:
Could not connect to LDAP server host localhost port 636 Error
netscape.ldap.LDAPException: IO Error creating JSS SSL Socket (-1)"}
Installation failed.

Expected results:

pkispawn should be successful

Additional info:

ca debug log messages also attached in
https://bugzilla.redhat.com/attachment.cgi?id=1044870
CA communicating to SSL enabled ldap was successful by following the steps in
https://bugzilla.redhat.com/show_bug.cgi?id=871171#c41

Metadata Update from @rpattath:
- Issue set to the milestone: 10.2.6

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/2014

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata