<div dir="ltr">Hi All, I'm still struggling with LDAPS. In Jules' previous email there is a mention of: <div><br><div><i>"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." </i></div><div><br></div><div>I am in this situation of using a cert created by my internal Domain CA. The steps I have taken:</div><div>1.) Exported the public key/cert for Client Authentication, Server Authentication from my Windows Domain Controller in DER encoded binary X.509(.CER) format</div><div>2.) copied this .CER to /etc/ssl/certs</div><div>3.) in /etc/ldap/ldap.conf I added:</div><div><i>TLS_CACERT /etc/ssl/certs/my-exported-ldaps-cert.cer</i> </div><div>This line sits under the original line of TLS_CACERT /etc/ssl/certs/ca-certificates.crt</div><div><br></div><div>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.</div><div><br></div><div>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).</div><div><br></div><div>Thank you,</div><div><br></div><div>Glenn</div><div> <i> </i><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 12, 2020 at 10:24 AM Jules Field 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">
<div>
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>
<tt> authLDAPServers1 =>
array('<a>ldaps://our-AD-server.soton.ac.uk</a>'),</tt><tt><br>
</tt><tt> authLDAPBaseDN1 => 'DC=soton,DC=ac,DC=uk',</tt><tt><br>
</tt><tt> authLDAPAccountSuffix1 => '@<a href="http://soton.ac.uk" target="_blank">soton.ac.uk</a>',</tt><tt><br>
</tt><tt> authLDAPUseSSL1 => false,</tt><tt><br>
</tt><tt> authLDAPUseTLS1 => false,</tt><tt><br>
</tt><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>
<br>
<div>On 10/02/2020 18:39, Scott Silva via
ZendTo wrote:<br>
</div>
<blockquote type="cite">
<pre>In my case I know the ports are open because I have a Linux based spam filter that is able to auth secured.
-----Original Message-----
From: ZendTo <a href="mailto:zendto-bounces@zend.to" target="_blank"><zendto-bounces@zend.to></a> On Behalf Of Guy Bertrand via ZendTo
Sent: Monday, February 10, 2020 10:37 AM
To: <a href="mailto:zendto@zend.to" target="_blank">zendto@zend.to</a>
Cc: Guy Bertrand <a href="mailto:Guy.Bertrand@exelaonline.com" target="_blank"><Guy.Bertrand@exelaonline.com></a>
Subject: [ZendTo] MS LDAPs
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:
- the outgoing firewall config on the ZendTo server
- the firewall on the DC (is port 636 open?)
- routing
- any intermediate firewall rules
Quick test: open a command prompt (CMD on Windows, any shell on *nix). This will try to "telnet" to that port.
C:\> telnet "ip of your DC" 636
If a blank screen appears then the port is open, and the test is successful.
If you receive a connecting... message or an error message then something is blocking that port.
Guy Bertrand, M.Ing
Directeur informatique / IT Manager
EXELA TECHNOLOGIES
b: +1.514.392.4999 | m: +1.514.265.9754
1155, boulevard Robert-Bourassa, suite 500 | Montréal (Québec) CANADA H3B 3A7 <a href="http://www.ExelaTech.com" target="_blank">www.ExelaTech.com</a> | EXELA LinkedIn
________________________________
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.
________________________________
Please consider the environment before printing or forwarding this email. If you do print this email, please recycle the paper.
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.
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.
_______________________________________________
ZendTo mailing list
<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a>
<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>
_______________________________________________
ZendTo mailing list
<a href="mailto:ZendTo@zend.to" target="_blank">ZendTo@zend.to</a>
<a href="http://jul.es/mailman/listinfo/zendto" target="_blank">http://jul.es/mailman/listinfo/zendto</a>
</pre>
</blockquote>
<br>
<pre cols="72">Jules
--
Julian Field MEng CEng CITP MBCS MIEEE MACM
'A good programmer is someone who always looks both ways
before crossing a one-way street.' - Doug Linder
<a href="http://www.Zend.To" target="_blank">www.Zend.To</a>
Twitter: @JulesFM
</pre>
</div>
_______________________________________________<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>