LDAPS TCP-636 shows as SSL

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

LDAPS TCP-636 shows as SSL

L3 Networker

Im creating a rule base to limit port access to a Domain Controller in a DMZ. I want to allow TCP/636 (or LDAPS) to this server as well as a group of other applications.

The only problem is that there is no LDAPS application defined. The application LDAP is defined as TCP/389 as it should be. LDAP also has TCP/636 defined but the PA does not identify TCP636 as LDAP traffic. I even created a new application LDAPS as TCP636 but the PA only recognizes it as application SSL over TCP/636. That would be fine but I dont want to create a new rule for a Service Object, I want to include it in the applications group. Nor do I want to allow all SSL to the domain controller.

Any thoughts ? Thanks,



L6 Presenter


Or rather LDAP within SSL-tunnel.

In order to make your PA to identify this properly you need to enable SSL-termination (SSL-decrypt).

  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!