Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-19-2015 09:48 AM
Hello.
I am trying to setup an application policy rule to allow secure LDAP from our hosting company back to our internal domain controller running MS AD. I have the appropriate NAT statement setup.
If you look in the log screenshot above, you'll see that the first entry is being denied. For my list of allowed applications in that rule, I have added LDAP and SSL. My services tab is set at Application-default.
For testing, I also tried just using regular LDAP with with just LDAP for application allowed, and services as Application-default. That worked fine, as you can see in log entry 2-8.
Do I need to change the services to TCP-636 to get LDAPS to work? I looked at the LDAP application object, and it lists 389, 636 as the ports it uses.
Thanks.
Dannon
02-19-2015 12:24 PM
Hi dannon
You will have to allow SSL on service TCP-636 to make this work.
Firewall will not be able to identify it as LDAP unless you enable decryption.
02-19-2015 12:24 PM
Hi dannon
You will have to allow SSL on service TCP-636 to make this work.
Firewall will not be able to identify it as LDAP unless you enable decryption.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
