<?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: Globalprotect Self Signed certificate with Chrome in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/578857#M5050</link>
    <description>&lt;P&gt;Can anyone update the resolution of this ?&lt;/P&gt;</description>
    <pubDate>Thu, 29 Feb 2024 15:51:28 GMT</pubDate>
    <dc:creator>LamThong</dc:creator>
    <dc:date>2024-02-29T15:51:28Z</dc:date>
    <item>
      <title>Globalprotect Self Signed certificate with Chrome</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/571634#M4772</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Starting from one or two month ago, maybe after a Chrome update, I'm unable to open the globalprotect login page on my firewall with Google Chrome.&lt;/P&gt;
&lt;P&gt;It doesn't depends on the client OS, it happens wth Google Chrome (all other browser are working fine).&lt;/P&gt;
&lt;P&gt;The error I get is "ERR_SSL_KEY_USAGE_INCOMPATIBLE".&lt;/P&gt;
&lt;P&gt;The certificate is generated by the firewall.&lt;/P&gt;
&lt;P&gt;The only temp fix I found is to set manually this registry key&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome]&lt;/DIV&gt;
&lt;DIV&gt;"RSAKeyUsageForLocalAnchorsEnabled"=dword:00000000&lt;/DIV&gt;
&lt;DIV&gt;Do you have noticed that?&lt;/DIV&gt;
&lt;DIV&gt;Thankk you&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 03 Jan 2024 18:20:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/571634#M4772</guid>
      <dc:creator>NextGeneration</dc:creator>
      <dc:date>2024-01-03T18:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: Globalprotect Self Signed certificate with Chrome</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/578857#M5050</link>
      <description>&lt;P&gt;Can anyone update the resolution of this ?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 15:51:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/578857#M5050</guid>
      <dc:creator>LamThong</dc:creator>
      <dc:date>2024-02-29T15:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: Globalprotect Self Signed certificate with Chrome</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/590900#M5523</link>
      <description>&lt;P&gt;It is working via Firefox.&lt;/P&gt;
&lt;P&gt;I have the same problem.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And your workaround does not work for me.&lt;/P&gt;
&lt;P&gt;Can you post detailed instruction about creating this registry file.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 08:26:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-self-signed-certificate-with-chrome/m-p/590900#M5523</guid>
      <dc:creator>stefan.tomasevic</dc:creator>
      <dc:date>2024-07-02T08:26:32Z</dc:date>
    </item>
  </channel>
</rss>

