Hello All,
Im trying to setup syncrepl with TLS. But so far it won´t work. Actually Im a bit confused because Provider.log says "TLS established" and consumer.log "ldap_start_tls failed (-11)".
My settings are as follows:
provider slapd.conf:
overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 100
consumer slapd.conf:
index entryCSN,entryUUID eq
syncrepl rid=123 starttls=yes provider=ldap://ldapmaster:389 type=refreshAndPersist interval=00:00:00:01 searchbase="dc=test,dc=de" filter="(objectclass=*)" scope=sub attrs="*" schemachecking=off updatedn="cn=syncuser,ou=system,dc=test,dc=de" credentials="xxx" bindmethod=simple binddn="cn=admin,dc=uni-koblenz-landau,dc=de" credentials="xxx"
provider.log:
Dec 5 15:40:57 testldap slapd[8997]: conn=2 op=3 UNBIND Dec 5 15:40:57 testldap slapd[8997]: conn=2 fd=15 closed Dec 5 15:41:01 testldap slapd[8997]: conn=3 fd=15 ACCEPT from IP=192.168.1.2:50400 (IP=0.0.0.0:389) Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=0 STARTTLS Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=0 RESULT oid= err=0 text= Dec 5 15:41:01 testldap slapd[8997]: conn=3 fd=15 TLS established tls_ssf=256 ssf=256 Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=1 BIND dn="cn=admin,dc=test,dc=de" method=128 Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=1 BIND dn="cn=admin,dc=test,dc=de" mech=SIMPLE ssf=0 Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=1 RESULT tag=97 err=0 text= Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=2 SRCH base="dc=test,dc=de" scope=2 deref=0 filter="(objectClass=*)" Dec 5 15:41:01 testldap slapd[8997]: conn=3 op=2 SRCH attr=* structuralObjectClass entryCSN
consumer.log:
Dec 5 14:49:50 TESTNETZ-BDC slapd[6513]: slapd starting Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: Warning: rid 123 ldap_start_tls failed (-11) Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 fd=25 ACCEPT from IP=127.0.0.1:54163 (IP=0.0.0.0:389) Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 op=0 BIND dn="" method=128 Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 op=0 RESULT tag=97 err=0 text= Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 op=1 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 op=2 UNBIND Dec 5 14:49:51 TESTNETZ-BDC slapd[6513]: conn=0 fd=25 closed
Does someone know what part of the setup could be wrong? Are there more config files needed?
I would appreciate any help or hint!
Thank you!
Cristian
--On December 5, 2007 3:17:01 PM +0100 Cristian Laufer laufer@uni-koblenz-landau.de wrote:
Hello All, syncrepl rid=123 starttls=yes provider=ldap://ldapmaster:389
TLS generally required FQDN's. Fix your provider URL.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Hello Quanah,
sorry, I am actually using:
provider=ldap://192.168.0.7:389
Would that be ok to use?
Cristian
Quanah Gibson-Mount schrieb:
--On December 5, 2007 3:17:01 PM +0100 Cristian Laufer laufer@uni-koblenz-landau.de wrote:
Hello All, syncrepl rid=123 starttls=yes provider=ldap://ldapmaster:389
TLS generally required FQDN's. Fix your provider URL.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
What did you use when you generated your certificate? Important thing is that they match.
-----Original Message----- From: openldap-software-bounces+jeff_clowser=fanniemae.com@openldap.org [mailto:openldap-software-bounces+jeff_clowser=fanniemae.com@openldap.org] On Behalf Of Cristian Laufer Sent: Thursday, December 06, 2007 9:50 AM To: Quanah Gibson-Mount; openldap-software@openldap.org Subject: Re: syncrepl - ldap_start_tls failed (-11)
Hello Quanah,
sorry, I am actually using:
provider=ldap://192.168.0.7:389
Would that be ok to use?
Cristian
Quanah Gibson-Mount schrieb:
--On December 5, 2007 3:17:01 PM +0100 Cristian Laufer laufer@uni-koblenz-landau.de wrote:
Hello All, syncrepl rid=123 starttls=yes provider=ldap://ldapmaster:389
TLS generally required FQDN's. Fix your provider URL.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
On Thursday 06 December 2007 16:50:16 Cristian Laufer wrote:
Hello Quanah,
sorry, I am actually using:
provider=ldap://192.168.0.7:389
Would that be ok to use?
Cristian
Quanah Gibson-Mount schrieb:
--On December 5, 2007 3:17:01 PM +0100 Cristian Laufer
laufer@uni-koblenz-landau.de wrote:
Hello All, syncrepl rid=123 starttls=yes provider=ldap://ldapmaster:389
TLS generally required FQDN's. Fix your provider URL.
The name you provide to the software must match the subject CN on the cert.
However, instead of guessing, why don't you rather do an ldapsearch, exactly as your syncrepl is configured, with SSL enabled etc., until you can get ldapsearch to accept the cert.
I haven't tried a subjectCN of an IP, but I suspect that wouldn't work, you would rather use a subjectAlternateName=IP:192.168.0.7 ... but you should rather just use a hostname (entry in /etc/hosts if necessary to get it to the right IP) that matches the subjectCN on the cert.
Regards, Buchan
openldap-software@openldap.org