<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic LDAPS TCP-636 shows as SSL in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps-tcp-636-shows-as-ssl/m-p/19590#M14311</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts ? Thanks,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Justin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 01 Apr 2013 17:42:07 GMT</pubDate>
    <dc:creator>jhickey</dc:creator>
    <dc:date>2013-04-01T17:42:07Z</dc:date>
    <item>
      <title>LDAPS TCP-636 shows as SSL</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps-tcp-636-shows-as-ssl/m-p/19590#M14311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts ? Thanks,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Justin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Apr 2013 17:42:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps-tcp-636-shows-as-ssl/m-p/19590#M14311</guid>
      <dc:creator>jhickey</dc:creator>
      <dc:date>2013-04-01T17:42:07Z</dc:date>
    </item>
    <item>
      <title>Re: LDAPS TCP-636 shows as SSL</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps-tcp-636-shows-as-ssl/m-p/19591#M14312</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;LDAPS is SSL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or rather LDAP within SSL-tunnel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to make your PA to identify this properly you need to enable SSL-termination (SSL-decrypt).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Apr 2013 20:31:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps-tcp-636-shows-as-ssl/m-p/19591#M14312</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-01T20:31:37Z</dc:date>
    </item>
  </channel>
</rss>

