<?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 Old certificate showing even after new certificate mapped to the ssl profile in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252360#M71744</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using&amp;nbsp;&lt;SPAN&gt;Software Version - 8.0.8, Global Protect Agent - 4.0.4&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One user&amp;nbsp;&lt;SPAN&gt;is able to connect the VPN through portal but when accessed the URL from the internet still seeing the old certificate after new certificated mapped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried&amp;nbsp;&lt;SPAN&gt;to reinstall the GlobalProtect client by accessing the GlobalProtect portal so the client pulls the latest certificate but no luck.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any idea how to fix this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Tue, 05 Mar 2019 21:10:19 GMT</pubDate>
    <dc:creator>FarzanaMustafa</dc:creator>
    <dc:date>2019-03-05T21:10:19Z</dc:date>
    <item>
      <title>Old certificate showing even after new certificate mapped to the ssl profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252360#M71744</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using&amp;nbsp;&lt;SPAN&gt;Software Version - 8.0.8, Global Protect Agent - 4.0.4&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One user&amp;nbsp;&lt;SPAN&gt;is able to connect the VPN through portal but when accessed the URL from the internet still seeing the old certificate after new certificated mapped.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We tried&amp;nbsp;&lt;SPAN&gt;to reinstall the GlobalProtect client by accessing the GlobalProtect portal so the client pulls the latest certificate but no luck.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any idea how to fix this?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 21:10:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252360#M71744</guid>
      <dc:creator>FarzanaMustafa</dc:creator>
      <dc:date>2019-03-05T21:10:19Z</dc:date>
    </item>
    <item>
      <title>Re: Old certificate showing even after new certificate mapped to the ssl profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252491#M71766</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/98673"&gt;@FarzanaMustafa&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This sounds like a client browser issue more than anything else. If the user accesses the portal via a different browser (such as Firefox/Chrome) do they still receive the old certificate?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2019 14:06:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252491#M71766</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-03-06T14:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: Old certificate showing even after new certificate mapped to the ssl profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252782#M71836</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp; yes it is happening in all browsers.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2019 23:46:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252782#M71836</guid>
      <dc:creator>FarzanaMustafa</dc:creator>
      <dc:date>2019-03-07T23:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: Old certificate showing even after new certificate mapped to the ssl profile</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252792#M71837</link>
      <description>&lt;P&gt;If you're not interested in root cause or a real solution and just want to get past this issue, you can try a commit force from CLI or if you want to be even more aggressive you can restart the management plane (debug software restart process management-server).&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;8.0.8 is about a year old and is also 8 maintenance revisions back. There aren't any clear fixes in the release notes that account for this specific behavior, there are several medium- and high-priority vulnerabilities fixed since then it may be worth upgrading first to see if the issue is resolved. Doing the upgrade also does a system restart and a commit, so you can get up to a more current version and try the debugging steps above at the same time if you're able to upgrade.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Mar 2019 01:06:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/old-certificate-showing-even-after-new-certificate-mapped-to-the/m-p/252792#M71837</guid>
      <dc:creator>gwesson</dc:creator>
      <dc:date>2019-03-08T01:06:14Z</dc:date>
    </item>
  </channel>
</rss>

