Hello Chad, PacketFence ignores the certificate by default, so just configure the port 636 on the AD LDAP source and it should be good.
Thanks, Ludovic Zammit [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x145) :: www.inverse.ca <http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>) and PacketFence (http://packetfence.org <http://packetfence.org/>) > On May 7, 2020, at 4:05 PM, Chad Jemison via PacketFence-users > <[email protected]> wrote: > > Hello, > > I am trying to enable LDAP SSL in my authentication source. I have a Windows > PKI and have imported the certificate, key, and intermediate certificates for > both HTTP and RADIUS now. Is there something I am missing to enable secure > LDAP lookups with Packetfence? > > My domain controllers have certificates from our internal CA. I am able to > test using ldp.exe on my desktop with port 636 to my DC and it connects and > shows that SSL is enabled. > > > > > --------------------------------------------------------------- > Chad Jemison > Director of IT > Seneca Gaming Authority <http://www.sni.org/sga> > 345 Third Street, Suite 404 > Niagara Falls, New York 14303 > 716-299-1246 x267 > > _______________________________________________ > PacketFence-users mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/packetfence-users > <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
