<?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: VPN through Gateway Browsing HTTPS residual certificate issue in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39529#M13865</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vladimir,&lt;/P&gt;&lt;P&gt;Good Document.&lt;/P&gt;&lt;P&gt;We import either new certificate or renew the certificate if it is expired but if certificate is still valid and you import new one then you should remove the older one otherwise it points to older one.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Mar 2018 11:01:02 GMT</pubDate>
    <dc:creator>Gaurav_Pandya</dc:creator>
    <dc:date>2018-03-26T11:01:02Z</dc:date>
    <item>
      <title>VPN through Gateway Browsing HTTPS residual certificate issue</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39528#M13864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With HTTPS inspection configured and Outbound Certificate distributed, following behavior being observed:&lt;/P&gt;&lt;P&gt;From internal hosts, browsers reaching destination, substituted certificate is shown as valid and there are no indications of the intercept:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;IMG class="jive-image image-4" src="https://community.checkpoint.com/legacyfs/online/checkpoint/64074_pastedImage_4.png" style="width: 323px; height: 297px;" /&gt;&amp;nbsp;&amp;nbsp;&lt;IMG class="image-5 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/64075_pastedImage_5.png" style="width: 368px; height: 529px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When remote client (Endpoint VPN) establishes the connection to the same site, certificate is substituted, declared "valid", but the browser indicates the site being "Not&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Secure":&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-2 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/64072_pastedImage_2.png" style="width: 365px; height: 346px;" /&gt;&amp;nbsp;&lt;IMG class="image-3 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/64073_pastedImage_3.png" style="width: 339px; height: 479px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Certificate is installed on the remote client in Trusted Root Certification Authorities:&lt;/P&gt;&lt;P&gt;&lt;IMG class="image-6 jive-image" src="https://community.checkpoint.com/legacyfs/online/checkpoint/64076_pastedImage_6.png" style="border: 0px; margin: 2px 20px 0px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The culprit was the older certificate issued by the same gateway and installed on clients. After removal of the old certificate, clients' browsers behavior reverted to normal.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 25 Mar 2018 22:05:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39528#M13864</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-03-25T22:05:31Z</dc:date>
    </item>
    <item>
      <title>Re: VPN through Gateway Browsing HTTPS residual certificate issue</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39529#M13865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vladimir,&lt;/P&gt;&lt;P&gt;Good Document.&lt;/P&gt;&lt;P&gt;We import either new certificate or renew the certificate if it is expired but if certificate is still valid and you import new one then you should remove the older one otherwise it points to older one.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2018 11:01:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39529#M13865</guid>
      <dc:creator>Gaurav_Pandya</dc:creator>
      <dc:date>2018-03-26T11:01:02Z</dc:date>
    </item>
    <item>
      <title>Re: VPN through Gateway Browsing HTTPS residual certificate issue</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39530#M13866</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Too bad there is no CRL mechanism interface in Check Point that makes it manageable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2018 12:47:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/VPN-through-Gateway-Browsing-HTTPS-residual-certificate-issue/m-p/39530#M13866</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2018-03-26T12:47:17Z</dc:date>
    </item>
  </channel>
</rss>

