<?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 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549260#M112085</link>
    <description>&lt;P&gt;&amp;nbsp;I am in the process of setting up LDAPS on an 850. I created an LDAPS server profile and pinted it to our server for credentials. Aftr creating that, I set up an Authentication profile and Authentication sequence (wasnt sure if it was needed but the documentation said it was optional. I created an admin account that has the authentication profile in it. I am still unable to use my AD credentials. Do I need to make a security and authentication profile as well?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also went in to the command line and tested the authentication profile. I get this error message:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Failed to create a session with LDAP server&lt;/P&gt;
&lt;P&gt;Authentication failed against LDAP server at &amp;lt;ip address&amp;gt; for user "user"&lt;/P&gt;</description>
    <pubDate>Thu, 13 Jul 2023 15:50:37 GMT</pubDate>
    <dc:creator>m.maldonado</dc:creator>
    <dc:date>2023-07-13T15:50:37Z</dc:date>
    <item>
      <title>LDAPS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549260#M112085</link>
      <description>&lt;P&gt;&amp;nbsp;I am in the process of setting up LDAPS on an 850. I created an LDAPS server profile and pinted it to our server for credentials. Aftr creating that, I set up an Authentication profile and Authentication sequence (wasnt sure if it was needed but the documentation said it was optional. I created an admin account that has the authentication profile in it. I am still unable to use my AD credentials. Do I need to make a security and authentication profile as well?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I also went in to the command line and tested the authentication profile. I get this error message:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Failed to create a session with LDAP server&lt;/P&gt;
&lt;P&gt;Authentication failed against LDAP server at &amp;lt;ip address&amp;gt; for user "user"&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 15:50:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549260#M112085</guid>
      <dc:creator>m.maldonado</dc:creator>
      <dc:date>2023-07-13T15:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: LDAPS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549283#M112088</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/284777"&gt;@m.maldonado&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thanks for posting.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To start with, could you go through this&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000CqYPCA0" target="_self"&gt;KB&lt;/A&gt;&amp;nbsp;to perform basic diagnostic and collect more logs. The&amp;nbsp;authd.log should give you ultimate answer what the problem is. Also make sure that Bind and Base DN are correct. Note: To use LDAPS you have to import certificates used by LDAPS server to Firewall to form LDAP over SSL session. If this server is part of the AD, then you should import to Firewall root, intermediate, site CA certificates to have full certificate trust.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 21:23:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549283#M112088</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2023-07-13T21:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: LDAPS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549285#M112089</link>
      <description>&lt;P&gt;I realized I said profilies when I meant to say policies. Will those need to created as well?&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 21:36:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549285#M112089</guid>
      <dc:creator>m.maldonado</dc:creator>
      <dc:date>2023-07-13T21:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: LDAPS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549286#M112090</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/284777"&gt;@m.maldonado&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thank you for reply.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;By default the LDAP is using management interface for this communication, therefore there is no security policy required to allow this traffic. Have you set up a service route for LDAP to communicate over data plane interfaces? The reference is in this&amp;nbsp;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClpoCAC" target="_self"&gt;KB&lt;/A&gt;&amp;nbsp;Point No.3&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind Regards&lt;/P&gt;
&lt;P&gt;Pavel&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jul 2023 21:41:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549286#M112090</guid>
      <dc:creator>PavelK</dc:creator>
      <dc:date>2023-07-13T21:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: LDAPS</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549383#M112101</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;Check the logs to see if/where the traffic is getting blocked. If allowed on the Palo Alto, it could the LDAPS server blocking you so check its firewall if it has one. Also try just LDAP as a test and see if that works.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jul 2023 15:09:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ldaps/m-p/549383#M112101</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2023-07-14T15:09:45Z</dc:date>
    </item>
  </channel>
</rss>

