<?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: authorization issues in our tennant in Data Movement &amp; Streaming</title>
    <link>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517631#M3257</link>
    <description>&lt;P&gt;That was it, thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 13 May 2025 09:46:53 GMT</pubDate>
    <dc:creator>loki20beta</dc:creator>
    <dc:date>2025-05-13T09:46:53Z</dc:date>
    <item>
      <title>authorization issues in our tennant</title>
      <link>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517597#M3254</link>
      <description>&lt;P&gt;We are trying to access the tenant we have and we don't use it often. Today I got this when navigating to tennant address. Instead of&amp;nbsp;&lt;A href="https://TENNANT-address.us.qlikcloud.com/" target="_blank" rel="noopener"&gt;https://TENNANT-address.us.qlikcloud.com/&lt;/A&gt; it send to &lt;A href="https://dev-l1cbldpnpskjgnb8.us.auth0.com/u/login?state=hKF" target="_blank" rel="noopener"&gt;https://dev-l1cbldpnpskjgnb8.us.auth0.com/u/login?state=hKF&lt;/A&gt;. . Did Qlik accidentally used dev keys? Did is happen only to us or someone else?&lt;BR /&gt;&lt;BR /&gt;PS: it wasn't qlik, it was us&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 09:47:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517597#M3254</guid>
      <dc:creator>loki20beta</dc:creator>
      <dc:date>2025-05-13T09:47:43Z</dc:date>
    </item>
    <item>
      <title>Re: authorization issues in our tennant</title>
      <link>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517604#M3256</link>
      <description>&lt;P class=""&gt;Check if a custom Identity Provider was added. You can verify this in &lt;STRONG&gt;Administration → Identity Provider&lt;/STRONG&gt;.&lt;/P&gt;&lt;P class=""&gt;A common reason for having a custom Identity Provider is the use of the &lt;A href="https://qlik.dev/embed/qlik-embed/" target="_blank" rel="noopener"&gt;qlik-embed framework&lt;/A&gt; to integrate Qlik objects into external web applications.&lt;/P&gt;&lt;P class=""&gt;More details on why Identity Providers are needed in that context can be found here:&lt;BR /&gt;&lt;A href="https://qlik.dev/embed/qlik-embed/quickstart/qlik-embed-webcomponent-quickstart/#10-setup-an-oauth-client-application-in-your-qlik-cloud-tenant" target="_blank" rel="noopener"&gt;Qlik Embed Web Component Quick Start&lt;/A&gt;&lt;/P&gt;&lt;P class=""&gt;If you no longer need the active third-party Identity Provider, you can simply deactivate it — the default authentication flow will be restored automatically.&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 07:30:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517604#M3256</guid>
      <dc:creator>NickGogin</dc:creator>
      <dc:date>2025-05-13T07:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: authorization issues in our tennant</title>
      <link>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517631#M3257</link>
      <description>&lt;P&gt;That was it, thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 13 May 2025 09:46:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Data-Movement-Streaming/authorization-issues-in-our-tennant/m-p/2517631#M3257</guid>
      <dc:creator>loki20beta</dc:creator>
      <dc:date>2025-05-13T09:46:53Z</dc:date>
    </item>
  </channel>
</rss>

