<div dir="ltr">Thank you Scott,<div><br></div><div>I was able to complete your instructions but mine is still a no-go. I have verified that my Zend server is trying to connect over port 636, but I'm still getting errors. I will continue plugging away at this on Monday. </div><div><br></div><div>I'm glad you were able to get yours up and running. </div><div><br></div><div>Have a good weekend.</div><div><br></div><div>Glenn</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 14, 2020 at 12:23 PM Scott Silva via ZendTo <<a href="mailto:zendto@zend.to">zendto@zend.to</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">OK… I think I figured this out…<br>
<br>
Run openssl s_client -connect <a href="http://your-AD-server-here.example.com:636" rel="noreferrer" target="_blank">your-AD-server-here.example.com:636</a> (fixed to your AD server)<br>
<br>
In the results you will see a full key in base 64<br>
<br>
Copy all from the ----BEGIN Certificate --- to the ---END CERTIFICATE--- including those lines and paste to the end of whichever cert your TLS_CACERT points to<br>
<br>
Don't overwrite, paste to the end and save.<br>
Now try and see if it authenticates...<br>
<br>
Works in mine<br>
<br>
<br>
<br>
<br>
<br>
From: ZendTo <<a href="mailto:zendto-bounces@zend.to" target="_blank">zendto-bounces@zend.to</a>> On Behalf Of Glenn Noel via ZendTo<br>
Sent: Thursday, February 13, 2020 2:24 PM<br>
To: ZendTo Users <<a href="mailto:zendto@zend.to" target="_blank">zendto@zend.to</a>><br>
Cc: Glenn Noel <<a href="mailto:glenn.noel@gmail.com" target="_blank">glenn.noel@gmail.com</a>><br>
Subject: Re: [ZendTo] MS LDAPs<br>
<br>
Hi All, I'm still struggling with LDAPS. In Jules' previous email there is a mention of: <br>
<br>
"If you are using some sort of a self-signed or locally-signed certificate on your AD server(s), then you will need to add your local root CA public cert to the TLS_CACERT file, or else the ZendTo server won't be able to verify the cert it gets from the AD server. But if you are using a "normal" externally-signed commercial cert, it should work fine." <br>
<br>
I am in this situation of using a cert created by my internal Domain CA. The steps I have taken:<br>
1.) Exported the public key/cert for Client Authentication, Server Authentication from my Windows Domain Controller in DER encoded binary X.509(.CER) format<br>
2.) copied this .CER to /etc/ssl/certs<br>
3.) in /etc/ldap/ldap.conf I added:<br>
TLS_CACERT /etc/ssl/certs/my-exported-ldaps-cert.cer <br>
This line sits under the original line of TLS_CACERT /etc/ssl/certs/ca-certificates.crt<br>
<br>
It was a shot in the dark and I successfully predicted that it would not work. However I am stuck. If anyone has a good step-by-step to help me out I would appreciate it immensely.<br>
<br>
If the recommended method is to purchase a 3rd party cert please let me know - I will try that next (although I might need some assistance with that process too).<br>
<br>
Thank you,<br>
<br>
Glenn<br>
<br>
<br>
On Wed, Feb 12, 2020 at 10:24 AM Jules Field via ZendTo <mailto:<a href="mailto:zendto@zend.to" target="_blank">zendto@zend.to</a>> wrote:<br>
Scott,<br>
<br>
I have just done a CentOS 7 install of the latest ZendTo beta from scratch, including using SELinux.<br>
<br>
I set the preferences.php settings to<br>
<br>
authLDAPServers1 => array('ldaps://<a href="http://our-AD-server.soton.ac.uk" rel="noreferrer" target="_blank">our-AD-server.soton.ac.uk</a>'),<br>
authLDAPBaseDN1 => 'DC=soton,DC=ac,DC=uk',<br>
authLDAPAccountSuffix1 => '@<a href="http://soton.ac.uk" rel="noreferrer" target="_blank">http://soton.ac.uk</a>',<br>
authLDAPUseSSL1 => false,<br>
authLDAPUseTLS1 => false,<br>
<br>
and it just worked immediately. I didn't have to install any other packages at all.<br>
<br>
Our AD servers are listening on 636/tcp (the TCP port for ldaps according to /etc/services).<br>
<br>
I have already tested the same thing on Ubuntu 18.04 and it worked first time there too.<br>
<br>
If you are using some sort of a self-signed or locally-signed certificate on your AD server(s), then you will need to add your local root CA public cert to the TLS_CACERT file, or else the ZendTo server won't be able to verify the cert it gets from the AD server. But if you are using a "normal" externally-signed commercial cert, it should work fine.<br>
<br>
On 10/02/2020 18:39, Scott Silva via ZendTo wrote:<br>
In my case I know the ports are open because I have a Linux based spam filter that is able to auth secured.<br>
<br>
<br>
-----Original Message-----<br>
From: ZendTo mailto:<a href="mailto:zendto-bounces@zend.to" target="_blank">zendto-bounces@zend.to</a> On Behalf Of Guy Bertrand via ZendTo<br>
Sent: Monday, February 10, 2020 10:37 AM<br>
To: mailto:<a href="mailto:zendto@zend.to" target="_blank">zendto@zend.to</a><br>
Cc: Guy Bertrand mailto:<a href="mailto:Guy.Bertrand@exelaonline.com" target="_blank">Guy.Bertrand@exelaonline.com</a><br>
Subject: [ZendTo] MS LDAPs<br>
<br>
Reminder: LDAPS would normally use port 636 instead of ldap/389 to talk to the domain controller. Don't forget to check things between your ZendTo server and the domain controller:<br>
- the outgoing firewall config on the ZendTo server<br>
- the firewall on the DC (is port 636 open?)<br>
- routing<br>
- any intermediate firewall rules<br>
<br>
Quick test: open a command prompt (CMD on Windows, any shell on *nix). This will try to "telnet" to that port.<br>
C:\> telnet "ip of your DC" 636<br>
If a blank screen appears then the port is open, and the test is successful.<br>
If you receive a connecting... message or an error message then something is blocking that port.<br>
<br>
Guy Bertrand, M.Ing<br>
Directeur informatique / IT Manager<br>
EXELA TECHNOLOGIES<br>
b: +1.514.392.4999 | m: +1.514.265.9754<br>
1155, boulevard Robert-Bourassa, suite 500 | Montréal (Québec) CANADA H3B 3A7 <a href="http://www.ExelaTech.com" rel="noreferrer" target="_blank">http://www.ExelaTech.com</a> | EXELA LinkedIn<br>
<br>
<br>
________________________________<br>
Attention : le présent message et toutes les pièces jointes sont confidentiels et établis à l'attention exclusive du ou des destinataire(s) indiqué(s). Toute autre diffusion ou utilisation non autorisée est interdite. Si vous recevez ce message par erreur, veuillez immédiatement en avertir l'expéditeur par e-mail en retour, détruire le message et vous abstenir de toute référence aux informations qui y figurent afin d'éviter les sanctions attachées à la divulgation et à l'utilisation d'informations confidentielles. Les messages électroniques sont susceptibles d'altération. Exela Technologies et ses filiales déclinent toute responsabilité en cas d'altération ou de falsification du présent message.<br>
________________________________<br>
Please consider the environment before printing or forwarding this email. If you do print this email, please recycle the paper.<br>
<br>
This email message may contain confidential, proprietary and/or privileged information. It is intended only for the use of the intended recipient(s). If you have received it in error, please immediately advise the sender by reply email and then delete this email message. Any disclosure, copying, distribution or use of the information contained in this email message to or by anyone other than the intended recipient is strictly prohibited. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Exela Technologies, Inc. or its subsidiaries.<br>
<br>
This email does not constitute an agreement to conduct transactions by electronic means and does not create any legally binding contract or enforceable obligation against Exela in the absence of a fully signed written agreement.<br>
<br>
_______________________________________________<br>
ZendTo mailing list<br>
mailto:<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a><br>
<a href="http://jul.es/mailman/listinfo/zendto" rel="noreferrer" target="_blank">http://jul.es/mailman/listinfo/zendto</a><br>
<br>
_______________________________________________<br>
ZendTo mailing list<br>
mailto:<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a><br>
<a href="http://jul.es/mailman/listinfo/zendto" rel="noreferrer" target="_blank">http://jul.es/mailman/listinfo/zendto</a><br>
<br>
<br>
Jules<br>
<br>
-- <br>
Julian Field MEng CEng CITP MBCS MIEEE MACM<br>
<br>
'A good programmer is someone who always looks both ways<br>
before crossing a one-way street.' - Doug Linder<br>
<br>
<a href="http://www.Zend.To" rel="noreferrer" target="_blank">http://www.Zend.To</a><br>
Twitter: @JulesFM<br>
_______________________________________________<br>
ZendTo mailing list<br>
mailto:<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a><br>
<a href="http://jul.es/mailman/listinfo/zendto" rel="noreferrer" target="_blank">http://jul.es/mailman/listinfo/zendto</a><br>
_______________________________________________<br>
ZendTo mailing list<br>
<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a><br>
<a href="http://jul.es/mailman/listinfo/zendto" rel="noreferrer" target="_blank">http://jul.es/mailman/listinfo/zendto</a><br>
</blockquote></div>