<?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 Re: Global Protect portal authentication with LDAP fails in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38141#M27945</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which PANOS is running on your box ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Feb 2013 13:21:41 GMT</pubDate>
    <dc:creator>gafrol</dc:creator>
    <dc:date>2013-02-19T13:21:41Z</dc:date>
    <item>
      <title>Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38135#M27939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have set up GP to authenticate against an AD server . User group mapping has done and u can pull the users . However, whenever you try to connect with one of the&amp;nbsp; users from the GP client or portal web page ,&amp;nbsp; you get authentication&amp;nbsp; fails message . Connecting with local db works fine . Any ideas ? I saw an article about spaces in the authentication profile . The profile has no space it is called localAD. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 11:00:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38135#M27939</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T11:00:07Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38136#M27940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't know what the problem with LDAP against AD could be in your case, but for the same purpose I am using a Kerberos Server Profile and a Kerberos Authentiction Profile in order to authenticate GP users against our MS AD. It looks like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.PNG" class="jive-image-thumbnail jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/5671_Capture.PNG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Capture.PNG" class="jive-image-thumbnail jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/5672_Capture.PNG" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe you can give it a try ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Roland&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 11:07:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38136#M27940</guid>
      <dc:creator>gafrol</dc:creator>
      <dc:date>2013-02-19T11:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38137#M27941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Upgraded the client to 1.2.1 now localdb doesn't work . I do get the cert error and allow it to import it &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 11:26:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38137#M27941</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T11:26:23Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38138#M27942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did that and still doesnt work&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 12:15:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38138#M27942</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T12:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38139#M27943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Take small steps. Does localdb authentication work again ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 12:32:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38139#M27943</guid>
      <dc:creator>gafrol</dc:creator>
      <dc:date>2013-02-19T12:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38140#M27944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes . It does . I had to downgrade to 1.1.6 and use the original cert that was created when the box was deployed . Now I connect using local db , still no AD nor Kerberos connectivity &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 12:42:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38140#M27944</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T12:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38141#M27945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which PANOS is running on your box ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 13:21:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38141#M27945</guid>
      <dc:creator>gafrol</dc:creator>
      <dc:date>2013-02-19T13:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38142#M27946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;4.1.8 .&amp;nbsp; Had to call TAC and they got to work . DN binding was incorrect and we missed the samaccountname under ldap authentication&amp;nbsp; profile .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 14:58:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38142#M27946</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T14:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38143#M27947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That's why I'm using Kerberos for authentication, it's much easier no fiddling around with bindings and samaccountnames etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 15:14:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38143#M27947</guid>
      <dc:creator>gafrol</dc:creator>
      <dc:date>2013-02-19T15:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect portal authentication with LDAP fails</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38144#M27948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess , we shall use Kerberos on other deployments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2013 16:55:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-portal-authentication-with-ldap-fails/m-p/38144#M27948</guid>
      <dc:creator>usvi</dc:creator>
      <dc:date>2013-02-19T16:55:45Z</dc:date>
    </item>
  </channel>
</rss>

