<?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: SSL wildcard certificate for firewall SAML portal in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128530#M26159</link>
    <description>&lt;P&gt;Hello PhoneBoy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For SAML authentication the certificate is being uploaded here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CaptureSAML.JPG" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/13595i1C3479603FB12E8E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="CaptureSAML.JPG" alt="CaptureSAML.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The primary concern was how to introduce a company wildcard already signed certificate (*.domain.com) to the firewall.&lt;/P&gt;&lt;P&gt;I only found&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;sk69660&amp;nbsp;&lt;/SPAN&gt;describing a procedure starting with CSR and sending it to the 3rd part CA for signing etc.&lt;/P&gt;&lt;P&gt;But there is a way how to bypass CSR and proceed with already signed certificate.&lt;/P&gt;&lt;P&gt;we had a *x509.cer certificate with a *.key (private key)&amp;nbsp;&lt;/P&gt;&lt;P&gt;first step was to rename *x509.cer to *x509.crt&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;make sure that the CRT file has the full certificate chain up to a trusted root CA.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;second step was to combine *x509.crt with *.key&amp;nbsp;&lt;/P&gt;&lt;P&gt;this step is documented in&amp;nbsp;&lt;SPAN&gt;sk69660&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[Expert@gw]# cpopenssl pkcs12 -export -out Final_cert_name.p12 -in *x509.crt -inkey *.key&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then the last step is just to upload&amp;nbsp;it to the portal settings according to your picture or the other picture.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;All worked like a charm.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Juraj&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Sep 2021 09:54:19 GMT</pubDate>
    <dc:creator>Juraj_Skalny</dc:creator>
    <dc:date>2021-09-01T09:54:19Z</dc:date>
    <item>
      <title>SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/127806#M26157</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm wondering if there is any way how to install a company ssl wildcard certificate for the firewall SAML portal in order to avoid browser security warnings. There is a post where it is indicated this works but there is no how to listed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your help,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Juraj&lt;/P&gt;</description>
      <pubDate>Tue, 24 Aug 2021 09:49:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/127806#M26157</guid>
      <dc:creator>Juraj_Skalny</dc:creator>
      <dc:date>2021-08-24T09:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128139#M26158</link>
      <description>&lt;P&gt;Pretty sure this is where you configure it:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="image.png" style="width: 751px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/13546i0215B61304A0A96E/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Aug 2021 15:25:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128139#M26158</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-08-26T15:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128530#M26159</link>
      <description>&lt;P&gt;Hello PhoneBoy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For SAML authentication the certificate is being uploaded here.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="CaptureSAML.JPG" style="width: 400px;"&gt;&lt;img src="https://community.checkpoint.com/t5/image/serverpage/image-id/13595i1C3479603FB12E8E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="CaptureSAML.JPG" alt="CaptureSAML.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The primary concern was how to introduce a company wildcard already signed certificate (*.domain.com) to the firewall.&lt;/P&gt;&lt;P&gt;I only found&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;sk69660&amp;nbsp;&lt;/SPAN&gt;describing a procedure starting with CSR and sending it to the 3rd part CA for signing etc.&lt;/P&gt;&lt;P&gt;But there is a way how to bypass CSR and proceed with already signed certificate.&lt;/P&gt;&lt;P&gt;we had a *x509.cer certificate with a *.key (private key)&amp;nbsp;&lt;/P&gt;&lt;P&gt;first step was to rename *x509.cer to *x509.crt&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;make sure that the CRT file has the full certificate chain up to a trusted root CA.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;second step was to combine *x509.crt with *.key&amp;nbsp;&lt;/P&gt;&lt;P&gt;this step is documented in&amp;nbsp;&lt;SPAN&gt;sk69660&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[Expert@gw]# cpopenssl pkcs12 -export -out Final_cert_name.p12 -in *x509.crt -inkey *.key&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Then the last step is just to upload&amp;nbsp;it to the portal settings according to your picture or the other picture.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;All worked like a charm.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Juraj&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Sep 2021 09:54:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128530#M26159</guid>
      <dc:creator>Juraj_Skalny</dc:creator>
      <dc:date>2021-09-01T09:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128567#M26160</link>
      <description>&lt;P&gt;Ah, didn't know you were referring to the the SAML portal for Remote Access.&lt;BR /&gt;But yes, this makes sense: the cert you import needs to have the full certificate chain included and in the correct format.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Sep 2021 13:55:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/128567#M26160</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2021-09-01T13:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/154330#M26161</link>
      <description>&lt;P&gt;Hello Juraj and PhoneBoy,&lt;/P&gt;&lt;P&gt;Following this post I was able to successfully import the wildcard certificate of our company *.domain.com. I have a DNS record for vpn.domain.com resolving to the firewall's external IP address. When creating the site I receive the warning message, which I have to Trust, stating that the presented certificate name *.domain.com differs from the site name vpn.domain.com. There is also a security alert appearing everytime the Secure Remote VPN client is started - leading to multiple complains from employees.&lt;/P&gt;&lt;P&gt;When I open the Main URL in a browser &lt;A href="https://vpn.domain.com/saml-vpn" target="_blank"&gt;https://vpn.domain.com/saml-vpn&lt;/A&gt;&amp;nbsp;it redirects to &lt;A href="https://&amp;lt;firewall" target="_blank"&gt;https://&amp;lt;firewal_external_ip&amp;gt;/saml-vpn/Access&lt;/A&gt;, which most probably causes the observed security alert.&lt;/P&gt;&lt;P&gt;Is there a way to replace the redirect url without recreating the IDP object?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 11:39:48 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/154330#M26161</guid>
      <dc:creator>glyaskov</dc:creator>
      <dc:date>2022-08-02T11:39:48Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/154416#M26162</link>
      <description>&lt;P&gt;Found the issue. It seems that the MULTIPORTAL_HOSTNAME variable in /opt/CPshrd-R81/conf/multiportal/httpd-conf/saml-vpn/httpd.conf keep the IPv4 address, instead of vpn.domain.com FQDN. The issue was fixed by manually editing the value.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2022 07:57:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/154416#M26162</guid>
      <dc:creator>glyaskov</dc:creator>
      <dc:date>2022-08-03T07:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/199629#M37438</link>
      <description>&lt;P&gt;Hello Bro,&lt;/P&gt;&lt;P&gt;As I know, when SAML has never been imported a certificate at all, the "import" button will be available.&lt;/P&gt;&lt;P&gt;If it has been imported, a "replace" will be available.&lt;/P&gt;&lt;P&gt;If so, how do we take out the certificate? The issue here is that the company doesn't want to extend the certificate expired anymore. Just want to delete not replace. Is there a solution to delete it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks bro.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 13:16:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/199629#M37438</guid>
      <dc:creator>Fiqri_kurniawan</dc:creator>
      <dc:date>2023-12-04T13:16:03Z</dc:date>
    </item>
    <item>
      <title>Re: SSL wildcard certificate for firewall SAML portal</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/199666#M37447</link>
      <description>&lt;P&gt;This will most likely require GUIdbedit to remove from the relevant gateway object.&lt;BR /&gt;It will be a process similar to this for the HTTPS Inspection certificate:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk92870" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk92870&lt;/A&gt;&lt;BR /&gt;However, that's just a guess and you may to want consult with TAC for the exact steps: &lt;A href="https://help.checkpoint.com" target="_blank"&gt;https://help.checkpoint.com&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 17:58:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/SSL-wildcard-certificate-for-firewall-SAML-portal/m-p/199666#M37447</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-12-04T17:58:49Z</dc:date>
    </item>
  </channel>
</rss>

