<?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 Can QPS use http in RedirectURL for ticket authentication? in Integration, Extension &amp; APIs</title>
    <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-QPS-use-http-in-RedirectURL-for-ticket-authentication/m-p/111429#M1529</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is for ticket authentication in Qlik Sense. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Qlik Help, &lt;A href="https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Authentication-Solutions-Ticket-Solution.htm" title="https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Authentication-Solutions-Ticket-Solution.htm"&gt;https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Au…&lt;/A&gt;‌‌ link mentions below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;'All communication between the authentication module and the &lt;/SPAN&gt;&lt;SPAN class="CommonComponentsQPSName" style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Qlik Sense Proxy Service&lt;/SPAN&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt; (&lt;/SPAN&gt;&lt;SPAN class="CommonComponentsQPSName_Short" style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;QPS&lt;/SPAN&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;) uses Transport Layer Security (TLS) and must be authorized using certificates.'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Does that means QPS only use https to talk to authentication module? In RedirectURI, if we use Http, that means it is not allowed? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Kind regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Lisa&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Aug 2018 07:07:49 GMT</pubDate>
    <dc:creator>Lisa_Sun</dc:creator>
    <dc:date>2018-08-07T07:07:49Z</dc:date>
    <item>
      <title>Can QPS use http in RedirectURL for ticket authentication?</title>
      <link>https://community.qlik.com/t5/Integration-Extension-APIs/Can-QPS-use-http-in-RedirectURL-for-ticket-authentication/m-p/111429#M1529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is for ticket authentication in Qlik Sense. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Qlik Help, &lt;A href="https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Authentication-Solutions-Ticket-Solution.htm" title="https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Authentication-Solutions-Ticket-Solution.htm"&gt;https://help.qlik.com/en-US/sense/June2018/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Server-Security-Au…&lt;/A&gt;‌‌ link mentions below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;'All communication between the authentication module and the &lt;/SPAN&gt;&lt;SPAN class="CommonComponentsQPSName" style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Qlik Sense Proxy Service&lt;/SPAN&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt; (&lt;/SPAN&gt;&lt;SPAN class="CommonComponentsQPSName_Short" style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;QPS&lt;/SPAN&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;) uses Transport Layer Security (TLS) and must be authorized using certificates.'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Does that means QPS only use https to talk to authentication module? In RedirectURI, if we use Http, that means it is not allowed? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Kind regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #0f0f0f; font-family: 'Open Sans', Arial, sans-serif; font-size: 14px;"&gt;Lisa&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2018 07:07:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Integration-Extension-APIs/Can-QPS-use-http-in-RedirectURL-for-ticket-authentication/m-p/111429#M1529</guid>
      <dc:creator>Lisa_Sun</dc:creator>
      <dc:date>2018-08-07T07:07:49Z</dc:date>
    </item>
  </channel>
</rss>

