<?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: QlikSense SF Saml integration in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/QlikSense-SF-Saml-integration/m-p/1581396#M13623</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You do not need to change these for the SAML authentication to work.&lt;/P&gt;
&lt;P&gt;In fact, even if you change them, it will be ignored by Qlik Sense, as Qlik Sense only supports signed SAML AuthnRequests.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As error 400 is a generic error, which just means that the SAML response sent by the IdP (Salesforce in this case) did not contain the correct information, it is hard to say what went wrong here.&lt;/P&gt;
&lt;P&gt;If you look into the Qlik Sense Proxy Audit trace logs (C:\programdata\qlik\sense\logs\proxy\trace\servername_audit_proxy.txt), you should see a warning indicating what went wrong.&lt;/P&gt;
&lt;P&gt;Once you found the error, you can search in our knowledge base if there is a resolution for it:&lt;BR /&gt;&lt;A href="https://support.qlik.com/apex/QS_CoveoSearch#q=SAML&amp;amp;t=All&amp;amp;sort=relevancy" target="_blank"&gt;https://support.qlik.com/apex/QS_CoveoSearch#q=SAML&amp;amp;t=All&amp;amp;sort=relevancy&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;If you cannot find anything there, please provide the information in the article below so that I can take a look:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.qlik.com/articles/000041558" target="_blank"&gt;https://support.qlik.com/articles/000041558&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 17 May 2019 07:05:10 GMT</pubDate>
    <dc:creator>Damien_V</dc:creator>
    <dc:date>2019-05-17T07:05:10Z</dc:date>
    <item>
      <title>QlikSense SF Saml integration</title>
      <link>https://community.qlik.com/t5/Management-Governance/QlikSense-SF-Saml-integration/m-p/1580369#M13593</link>
      <description>&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;when generating SP metadata file in the virtual proxie created,&amp;nbsp;i retrieve below values :&amp;nbsp;&lt;/P&gt;&lt;P&gt;WantAssertionsSigned="true" AuthnRequestsSigned="true"&lt;/P&gt;&lt;P&gt;as i understand both should be "false" to enable SSO&lt;/P&gt;&lt;P&gt;when longing in recieve an error as below&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="400.jpg" style="width: 629px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/12085i6A493AEA516D6893/image-size/large?v=v2&amp;amp;px=999" role="button" title="400.jpg" alt="400.jpg" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why are they created as true ? and how can i change it ?&lt;/P&gt;&lt;P&gt;is in the creation of the IdP file in SF ?&lt;/P&gt;&lt;P&gt;any ideas ?&lt;/P&gt;&lt;P&gt;advanced thanks&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 20:51:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/QlikSense-SF-Saml-integration/m-p/1580369#M13593</guid>
      <dc:creator>ilanbaruch</dc:creator>
      <dc:date>2024-11-16T20:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: QlikSense SF Saml integration</title>
      <link>https://community.qlik.com/t5/Management-Governance/QlikSense-SF-Saml-integration/m-p/1581396#M13623</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You do not need to change these for the SAML authentication to work.&lt;/P&gt;
&lt;P&gt;In fact, even if you change them, it will be ignored by Qlik Sense, as Qlik Sense only supports signed SAML AuthnRequests.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As error 400 is a generic error, which just means that the SAML response sent by the IdP (Salesforce in this case) did not contain the correct information, it is hard to say what went wrong here.&lt;/P&gt;
&lt;P&gt;If you look into the Qlik Sense Proxy Audit trace logs (C:\programdata\qlik\sense\logs\proxy\trace\servername_audit_proxy.txt), you should see a warning indicating what went wrong.&lt;/P&gt;
&lt;P&gt;Once you found the error, you can search in our knowledge base if there is a resolution for it:&lt;BR /&gt;&lt;A href="https://support.qlik.com/apex/QS_CoveoSearch#q=SAML&amp;amp;t=All&amp;amp;sort=relevancy" target="_blank"&gt;https://support.qlik.com/apex/QS_CoveoSearch#q=SAML&amp;amp;t=All&amp;amp;sort=relevancy&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;If you cannot find anything there, please provide the information in the article below so that I can take a look:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.qlik.com/articles/000041558" target="_blank"&gt;https://support.qlik.com/articles/000041558&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 07:05:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/QlikSense-SF-Saml-integration/m-p/1581396#M13623</guid>
      <dc:creator>Damien_V</dc:creator>
      <dc:date>2019-05-17T07:05:10Z</dc:date>
    </item>
  </channel>
</rss>

