<?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 Global Protect Client Certificate Issue in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246225#M70135</link>
    <description>&lt;P&gt;Hi team&lt;/P&gt;&lt;P&gt;How can I implement in the Global Protect confuguration the use of client certificate and LDAP authentication as two factor authentication only for some user (or a user group) ? We had only rolled out private certificates from our PKI for some user that has access to sensitive services and these user should use their certificate as additional authentication for the global protect portal/gateway. All other user should able to connect without client certificate. How can I implent these scenario?&lt;/P&gt;&lt;P&gt;I only found this in the Global Protect portal/gateway configuration valid for all clients that connect.&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Andrea&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Jan 2019 07:32:46 GMT</pubDate>
    <dc:creator>mtsadmin</dc:creator>
    <dc:date>2019-01-16T07:32:46Z</dc:date>
    <item>
      <title>Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246225#M70135</link>
      <description>&lt;P&gt;Hi team&lt;/P&gt;&lt;P&gt;How can I implement in the Global Protect confuguration the use of client certificate and LDAP authentication as two factor authentication only for some user (or a user group) ? We had only rolled out private certificates from our PKI for some user that has access to sensitive services and these user should use their certificate as additional authentication for the global protect portal/gateway. All other user should able to connect without client certificate. How can I implent these scenario?&lt;/P&gt;&lt;P&gt;I only found this in the Global Protect portal/gateway configuration valid for all clients that connect.&lt;/P&gt;&lt;P&gt;Regards&lt;BR /&gt;Andrea&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 07:32:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246225#M70135</guid>
      <dc:creator>mtsadmin</dc:creator>
      <dc:date>2019-01-16T07:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246242#M70136</link>
      <description>&lt;P&gt;Certificate authentication is global to all users. you can have either just certificate auth, just ldap auth or both cert and ldap but&lt;/P&gt;&lt;P&gt;you cannot have both cert only and cert plus ldap on the same portal/gateway.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you could just use certificate authentication on the portal and then depending on the user group you could issue a different gateway, one with cert auth and one with ldap auth.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;you will need additional license for multiple gateways.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 11:10:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246242#M70136</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-01-16T11:10:26Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246243#M70137</link>
      <description>&lt;P&gt;if you only need this for access to restricted services then just use a security policy to only allow access to those needed services.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 11:12:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246243#M70137</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-01-16T11:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246244#M70138</link>
      <description>&lt;P&gt;Sure ! I have security policies that only allow the access to those people. But thats not the problem. The problem is that only a Username/password for authentication is not save enough for external access to the services. And I don't want to roll out hundred of private certificates for people that do not need this for access to non-sensitive services. For this scenario it would be helpful to have the additional certificate authorization only for restricted user.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Andrea&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 11:30:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246244#M70138</guid>
      <dc:creator>mtsadmin</dc:creator>
      <dc:date>2019-01-16T11:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246245#M70139</link>
      <description>&lt;P&gt;sure I understand.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;what you are trying to configure is not possible on the same portal or gateway.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Do you have a gateway license?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or, could you have a different portals for the different users?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 11:51:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246245#M70139</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-01-16T11:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246287#M70147</link>
      <description>&lt;P&gt;Actually we don't have gateway license.&lt;/P&gt;&lt;P&gt;And yes, I also thought about a different portal for this users but for this I need to add a second IP-address to the interface, is it right ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards Andrea&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 15:01:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246287#M70147</guid>
      <dc:creator>mtsadmin</dc:creator>
      <dc:date>2019-01-16T15:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246288#M70148</link>
      <description>&lt;P&gt;yes it would be best to add second IP address but you may be able to configure a new portal and gateway on a loopback address. (so 2 portals on same interface but on different ports)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have used it, it works well but i have never used it alongside an existing portal/gateway but should work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;here is a link but just search web for globalprotect loopback.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGKCA0" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClGKCA0&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 15:09:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246288#M70148</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-01-16T15:09:48Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246317#M70156</link>
      <description>&lt;P&gt;I would distribute certificates to all users. if using PKI then you can use Group Policy to install a certificate on domain logon.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Jan 2019 17:50:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246317#M70156</guid>
      <dc:creator>Mick_Ball</dc:creator>
      <dc:date>2019-01-16T17:50:08Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Client Certificate Issue</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246443#M70177</link>
      <description>&lt;DIV class="tw-swapa"&gt;&amp;nbsp;Unfortunately to most of the clients are Unix Computers ...&lt;/DIV&gt;&lt;DIV class="tw-swapa"&gt;But thank you for providing the solution for the second portal ..I will check this .&lt;BR /&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV class="tw-swapa"&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class="tw-swapa"&gt;Regards&lt;/DIV&gt;&lt;DIV class="tw-swapa"&gt;Andrea&lt;/DIV&gt;</description>
      <pubDate>Thu, 17 Jan 2019 09:39:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/global-protect-client-certificate-issue/m-p/246443#M70177</guid>
      <dc:creator>mtsadmin</dc:creator>
      <dc:date>2019-01-17T09:39:32Z</dc:date>
    </item>
  </channel>
</rss>

