<?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: SSO Ticketing method with SALESFORCE in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/SSO-Ticketing-method-with-SALESFORCE/m-p/469766#M1271609</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See the article "QlikView and SalesForce.com Single Sign On" &lt;A _jive_internal="true" class="loading" href="https://community.qlik.com/docs/DOC-3730"&gt;http://community.qlik.com/docs/DOC-3730&lt;/A&gt;&lt;/P&gt;&lt;P&gt;where a complete, documented and downloadable solution is available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In summary, you will embed in SalesForce an intermediate URL that receives Session parameters from SalesForce then performs WebTicket before redirecting the User to a QlikView URL. The intermediate URL will be physically hosted within your own environment (not on SalesForce) and THAT address should be trusted in the IP WhiteList.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 Apr 2013 10:26:09 GMT</pubDate>
    <dc:creator>MichaelRobertshaw</dc:creator>
    <dc:date>2013-04-19T10:26:09Z</dc:date>
    <item>
      <title>SSO Ticketing method with SALESFORCE</title>
      <link>https://community.qlik.com/t5/QlikView/SSO-Ticketing-method-with-SALESFORCE/m-p/469765#M1271607</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In normal website with web ticketing method, adding web servers ip alone as a trusted ip in QV config file is sufficient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But when we go for Sales force, the method is same or any difference is there ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Karthi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SSO-Ticketing-method-with-SALESFORCE/m-p/469765#M1271607</guid>
      <dc:creator>gainkarthi</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: SSO Ticketing method with SALESFORCE</title>
      <link>https://community.qlik.com/t5/QlikView/SSO-Ticketing-method-with-SALESFORCE/m-p/469766#M1271609</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See the article "QlikView and SalesForce.com Single Sign On" &lt;A _jive_internal="true" class="loading" href="https://community.qlik.com/docs/DOC-3730"&gt;http://community.qlik.com/docs/DOC-3730&lt;/A&gt;&lt;/P&gt;&lt;P&gt;where a complete, documented and downloadable solution is available.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In summary, you will embed in SalesForce an intermediate URL that receives Session parameters from SalesForce then performs WebTicket before redirecting the User to a QlikView URL. The intermediate URL will be physically hosted within your own environment (not on SalesForce) and THAT address should be trusted in the IP WhiteList.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Apr 2013 10:26:09 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/SSO-Ticketing-method-with-SALESFORCE/m-p/469766#M1271609</guid>
      <dc:creator>MichaelRobertshaw</dc:creator>
      <dc:date>2013-04-19T10:26:09Z</dc:date>
    </item>
  </channel>
</rss>

