<?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: Ticket url with http or https in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1641264#M11659</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. I tested using the ticket with HTTP and I did not have the issue you describe. Could you give more details on how you are doing it ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. You need to use the QRS API to update proxy settings with the new thumbprint.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/sense-developer/September2019/APIs/RepositoryServiceAPI/index.html?page=1307" target="_blank"&gt;https://help.qlik.com/en-US/sense-developer/September2019/APIs/RepositoryServiceAPI/index.html?page=1307&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Search for&amp;nbsp; &lt;SPAN class="token string"&gt;"sslBrowserCertificateThumbprint"&lt;/SPAN&gt; &lt;SPAN class="token punctuation"&gt;:&lt;/SPAN&gt; &lt;SPAN class="token string"&gt;"aeiou" &lt;/SPAN&gt;on this page&lt;/P&gt;</description>
    <pubDate>Wed, 30 Oct 2019 14:06:12 GMT</pubDate>
    <dc:creator>Damien_V</dc:creator>
    <dc:date>2019-10-30T14:06:12Z</dc:date>
    <item>
      <title>Ticket url with http or https</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1641066#M11653</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I can access the qlik hub with ticket URL. But it is not user friendly with a self signed certificate. So There are two way to resolved the issue:&lt;/P&gt;&lt;P&gt;1. Let the ticket url to http. I think it is the simple way to resolve the problem. But when I changed the ticket URL to http, the URL redirect me to the &lt;EM&gt;Authentication module redirect URI&lt;/EM&gt;(virtual proxy authentication setting). I have already allow http server with 80 port in proxy, but still not working. why?&lt;/P&gt;&lt;P&gt;2. If I still use https, the best solution is follow the&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/change-to-signed-server-proxy-certificate.htm&amp;nbsp;to" target="_blank"&gt;https://help.qlik.com/en-US/sense/June2019/Subsystems/ManagementConsole/Content/Sense_QMC/change-to-signed-server-proxy-certificate.htm&amp;nbsp;to&lt;/A&gt; set the certificate. I want to use Let's encrypt to auto update the certificate. But the question is how to update the &lt;EM&gt;SSL browser certificate thumbprint&lt;/EM&gt; via API?&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 04:13:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1641066#M11653</guid>
      <dc:creator>knightluffy</dc:creator>
      <dc:date>2024-11-16T04:13:44Z</dc:date>
    </item>
    <item>
      <title>Re: Ticket url with http or https</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1641264#M11659</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. I tested using the ticket with HTTP and I did not have the issue you describe. Could you give more details on how you are doing it ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. You need to use the QRS API to update proxy settings with the new thumbprint.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/sense-developer/September2019/APIs/RepositoryServiceAPI/index.html?page=1307" target="_blank"&gt;https://help.qlik.com/en-US/sense-developer/September2019/APIs/RepositoryServiceAPI/index.html?page=1307&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Search for&amp;nbsp; &lt;SPAN class="token string"&gt;"sslBrowserCertificateThumbprint"&lt;/SPAN&gt; &lt;SPAN class="token punctuation"&gt;:&lt;/SPAN&gt; &lt;SPAN class="token string"&gt;"aeiou" &lt;/SPAN&gt;on this page&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2019 14:06:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1641264#M11659</guid>
      <dc:creator>Damien_V</dc:creator>
      <dc:date>2019-10-30T14:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: Ticket url with http or https</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1642859#M11692</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry for my late reply.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. I have found the reason why the http not work. Because my url is like 'http://myserver/myvp/Hub?qlikTicket=zbs2j-XT0FnP01ov'. When I changed to&amp;nbsp;'http://myserver/myvp/Hub/?qlikTicket=zbs2j-XT0FnP01ov', it worked.&lt;/P&gt;&lt;P&gt;2. One more question, how to authenticate the APIs. I know that I can use client certificate via https with&amp;nbsp;&lt;SPAN&gt;Xrfkey in query , header and also set the X-Qlik-User like &lt;EM&gt;UserDirectory=Internal;UserId=sa_repository&lt;/EM&gt;. So where is the document for authenticate the APIs. Does&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/sense/June2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Server-Security-Authentication-Solutions.htm" target="_blank"&gt;https://help.qlik.com/en-US/sense/June2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Server-Security-Authentication-Solutions.htm&lt;/A&gt;&amp;nbsp;will work for these APIs?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2019 08:22:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Ticket-url-with-http-or-https/m-p/1642859#M11692</guid>
      <dc:creator>knightluffy</dc:creator>
      <dc:date>2019-11-05T08:22:00Z</dc:date>
    </item>
  </channel>
</rss>

