<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ticket on Stefan&#39;s Blog</title>
    <link>https://sstoichev.eu/categories/ticket/</link>
    <description>Recent content in Ticket on Stefan&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Wed, 05 Jan 2022 11:50:00 +0000</lastBuildDate>
    <atom:link href="https://sstoichev.eu/categories/ticket/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Web app authentication with QSEoW (web ticket &#43; session cookie)</title>
      <link>https://sstoichev.eu/post/web-app-authentication-with-qseow-web-ticket-session-cookie/</link>
      <pubDate>Wed, 05 Jan 2022 11:50:00 +0000</pubDate>
      <guid>https://sstoichev.eu/post/web-app-authentication-with-qseow-web-ticket-session-cookie/</guid>
      <description>&lt;p&gt;In one of the previous &lt;a href=&#34;__GHOST_URL__/2021/09/09/qseow-authentication-svelte/&#34;&gt;post&lt;/a&gt; we saw how to use web ticket to establish connection with Qlik Sense Engine. And probably for most cases the approach there is enough.&lt;/p&gt;
&lt;p&gt;But what if our web app have a requirement to communicate with other Qlik service(s) (in addition to the Engine)? For example, we want to list the reload tasks to which the user have access (this information is provided by &lt;a href=&#34;https://help.qlik.com/en-US/sense-developer/May2021/Subsystems/RepositoryServiceAPI/Content/Sense_RepositoryServiceAPI/RepositoryServiceAPI-Introduction.htm&#34;&gt;Qlik Repository Service REST API&lt;/a&gt;)?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
