I seem to be getting mixed information regarding the LDAP setup from support. Right now, we have the LDAP connection going over TLS on 636 but under the settings, the checkbox for requiring a valid certificate is unchecked. Sonicwall support says not to worry about the certificate as it still goes over Port 636 and is secure.

Integrating LDAP/Active Directory with SonicWall UTM Port Number: The default LDAP over TLS port number is TCP 636. The default LDAP (unencrypted) port number is TCP 389. If you are using a custom listening port on your LDAP server, specify it here. Server timeout (seconds): The amount of time, in seconds, that the SonicWall will wait for a response from the LDAP server before timing out LDAP client authentication failed | SonicWall Primary Domain: This must exactly match the domain name as shown on the LDAP server. User Tree for Login to Server: This refers to the OU that the Bind resides in. Again this must exactly match what's on the LDAP Server or the SonicWall's bind request will not be authenticated by the server. Configuration … How to Integrate LDAP / Active Directory with SonicWall The LDAP configuration with SonicWall Appliance is a very simple process. We can manage the users efficiently with user groups and assign privileges to a group of people. We can also enable Mirror LDAP users locally to retrieve the user information automatically in a specified interval. Integration of LDAP Groups or Local Groups and - SonicWall

How to Configure LDAP and enable DHA - sonicwall.com

In the LDAP configuration window, access the Users & Groups Tab and click Import Users. Select the appropriate LDAP server to import from along with the appropriate domain(s) to include. Choose the way in which you prefer user names to display. NOTE: This is a personal preference and does not affect Configuring LDAP Integration in SonicOS - SonicWall

Sep 30, 2014

PANEL_ldapProps - Technical Documentation - SonicWall The RADIUS to LDAP Relay feature is designed for use in a topology where there is a central site with an LDAP/AD server and a central SonicWALL with remote satellite sites connected into it via low-end SonicWALL security appliances that may not support LDAP. In that case the central SonicWALL can operate as a RADIUS server for the remote