<?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: Replacing Qlik Sense proxy SSL certificate causes 500 error on SAML authentication in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Replacing-Qlik-Sense-proxy-SSL-certificate-causes-500-error-on/m-p/1848770#M20439</link>
    <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;One of the most common issues we see at support for the 500 with SAML is related to&amp;nbsp;the new certificate using a hashing algorithm of SHA 256 .&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If that is the case you will need to verify the provider is set to "&lt;I&gt;Microsoft Enhanced RSA and AES Cryptographic Provider" .&amp;nbsp;&lt;/I&gt;If different, you will need to transform it so it uses the correct crypto provider info.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This article explains how to verify this setting and how to change the certificate attributes if needed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Knowledge/Error-500-Internal-server-error-in-the-Hub-QMC-when-connecting/ta-p/1710388?_ga=2.239594374.428252778.1620625576-2142895857.1617029380" target="_blank"&gt;https://community.qlik.com/t5/Knowledge/Error-500-Internal-server-error-in-the-Hub-QMC-when-connecting/ta-p/1710388?_ga=2.239594374.428252778.1620625576-2142895857.1617029380&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Tue, 19 Oct 2021 11:02:26 GMT</pubDate>
    <dc:creator>Alexis_Touet</dc:creator>
    <dc:date>2021-10-19T11:02:26Z</dc:date>
    <item>
      <title>Replacing Qlik Sense proxy SSL certificate causes 500 error on SAML authentication</title>
      <link>https://community.qlik.com/t5/Management-Governance/Replacing-Qlik-Sense-proxy-SSL-certificate-causes-500-error-on/m-p/1838719#M20263</link>
      <description>&lt;P&gt;I have a QSE Windows implementation that uses SAML authentication against Google Workplace.&lt;/P&gt;&lt;P&gt;When we attempt to update the SSL certificate on the server and paste the new thumbprint in the proxy config, authentication via the SAML Virtual Proxy starts returning a 500 error.&lt;/P&gt;&lt;P&gt;There are no changes to the SAML configuration (which has its own certificate).&amp;nbsp; Every post I find online references 500 errors related to the SAML certificate specifically.&lt;/P&gt;&lt;P&gt;Has anyone experienced similar issues?&amp;nbsp; I do not know how replacing the SSL cert on the proxy would cause a problem with the existing SAML configuration.&lt;/P&gt;&lt;P&gt;I understand the SP metadata could change in this scenario, but Google did not require us to upload the SP metadata into the SAML app.&lt;/P&gt;&lt;P&gt;I appreciate any advice/experience/guidance. Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 15 Nov 2024 23:42:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Replacing-Qlik-Sense-proxy-SSL-certificate-causes-500-error-on/m-p/1838719#M20263</guid>
      <dc:creator>greg-anderson</dc:creator>
      <dc:date>2024-11-15T23:42:00Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing Qlik Sense proxy SSL certificate causes 500 error on SAML authentication</title>
      <link>https://community.qlik.com/t5/Management-Governance/Replacing-Qlik-Sense-proxy-SSL-certificate-causes-500-error-on/m-p/1848770#M20439</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;One of the most common issues we see at support for the 500 with SAML is related to&amp;nbsp;the new certificate using a hashing algorithm of SHA 256 .&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;If that is the case you will need to verify the provider is set to "&lt;I&gt;Microsoft Enhanced RSA and AES Cryptographic Provider" .&amp;nbsp;&lt;/I&gt;If different, you will need to transform it so it uses the correct crypto provider info.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This article explains how to verify this setting and how to change the certificate attributes if needed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Knowledge/Error-500-Internal-server-error-in-the-Hub-QMC-when-connecting/ta-p/1710388?_ga=2.239594374.428252778.1620625576-2142895857.1617029380" target="_blank"&gt;https://community.qlik.com/t5/Knowledge/Error-500-Internal-server-error-in-the-Hub-QMC-when-connecting/ta-p/1710388?_ga=2.239594374.428252778.1620625576-2142895857.1617029380&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Oct 2021 11:02:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Replacing-Qlik-Sense-proxy-SSL-certificate-causes-500-error-on/m-p/1848770#M20439</guid>
      <dc:creator>Alexis_Touet</dc:creator>
      <dc:date>2021-10-19T11:02:26Z</dc:date>
    </item>
  </channel>
</rss>

