<?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: Qlik Alerting on Windows – Bug Summary (New Issues &amp;amp; SSO Fix Recap) in Reporting Service &amp; Alerting</title>
    <link>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2533873#M2594</link>
    <description>&lt;P&gt;I'm still encountering the same issue my Qlik Sense version is November 2024 release. My current Qlik Alerting version is November 2024 SR2.&lt;BR /&gt;I've already submitted a case with Qlik Support.&lt;BR /&gt;Has anyone else experienced this issue and found a resolution?&lt;/P&gt;</description>
    <pubDate>Tue, 21 Oct 2025 04:23:18 GMT</pubDate>
    <dc:creator>Amarender</dc:creator>
    <dc:date>2025-10-21T04:23:18Z</dc:date>
    <item>
      <title>Qlik Alerting on Windows – Bug Summary (New Issues &amp; SSO Fix Recap)</title>
      <link>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2518686#M2389</link>
      <description>&lt;P&gt;In working with Qlik Alerting for Windows, I’ve encountered several issues.&lt;BR /&gt;Here’s a categorized summary, including:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;1 newly discovered issue with core config&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;1 new issue with SSO in SR2&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Previously known SSO &amp;amp; extension issues&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; [1] Newly Discovered – Core Config Issue &lt;span class="lia-unicode-emoji" title=":exclamation_mark:"&gt;❗&lt;/span&gt; CSRF Token API Error (Missing Port When Using Non-Default HTTPS Port)&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;From &lt;STRONG&gt;Qlik Sense Nov 2024&lt;/STRONG&gt;, CSRF token validation is required&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Alerting now supports this (see doc: &lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Qlik-Alerting-403-errors-after-upgrading-to-Qlik-Sense-November/ta-p/2503902" target="_new" rel="noopener"&gt;https://community.qlik.com/t5/Official-Support-Articles/Qlik-Alerting-403-errors-after-upgrading-to-Qlik-Sense-November/ta-p/2503902&lt;/A&gt;)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;However, &lt;STRONG&gt;if you use a non-default port (e.g., 8443)&lt;/STRONG&gt;, CSRF token fetch fails with 403&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Debugging server.js shows the CSRF token URL &lt;STRONG&gt;omits the port&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; [2] SSO Integration – Issues (1 New + 2 Previously Documented)&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;Full breakdown of earlier issues here:&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Reporting-Service-Alerting/Issue-and-Solution-for-SSO-Integration-between-Qlik-Sense/td-p/2506735" target="_new" rel="noopener"&gt;https://community.qlik.com/t5/Reporting-Service-Alerting/Issue-and-Solution-for-SSO-Integration-between-Qlik-Sense/td-p/2506735&lt;/A&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;HR /&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":new_button:"&gt;🆕&lt;/span&gt; &lt;STRONG&gt;(New in SR2)&lt;/STRONG&gt; Test Connection Error in SSO Mode&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Appears in &lt;STRONG&gt;SR2 only&lt;/STRONG&gt; – SR1 behaves correctly&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;When clicking “Test Connection”, result shows:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;"Invalid SSO URL. Please contact your administrator."&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Yet actual login works fine&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Workarounds:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Modify the MongoDB config manually under qlikalerting &amp;gt; source&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Or: Use Basic Auth → Save → Switch to SSO mode → Save again&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":pushpin:"&gt;📌&lt;/span&gt; Previously Identified Issues&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;In qaw_sso.html, getQlikURL() parses URL based on /sense → should use /content&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Port is missing in constructed URL → breaks non-default port configs&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;HR /&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; [3] Extension Bug (Previously Noted)&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;request.js in qlik-alerting-extension.zip includes a getQlikURL() function with no port in result&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;This function works contextually in /sense, so no immediate issue there&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Likely reused in SSO code without necessary adjustments&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;HR /&gt;&lt;P&gt;If you’ve faced any of these issues, I’d appreciate your input or confirmations in the comments.&lt;BR /&gt;And if any Qlik engineers see this:&lt;BR /&gt;&lt;STRONG&gt;Can these be tracked as formal bugs or passed to engineering?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Thanks for reading!&lt;/P&gt;&lt;P&gt;&lt;LI-PRODUCT title="Qlik Alerting" id="qlikAlerting"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 May 2025 14:29:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2518686#M2389</guid>
      <dc:creator>zolbae</dc:creator>
      <dc:date>2025-05-22T14:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Alerting on Windows – Bug Summary (New Issues &amp; SSO Fix Recap)</title>
      <link>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2533873#M2594</link>
      <description>&lt;P&gt;I'm still encountering the same issue my Qlik Sense version is November 2024 release. My current Qlik Alerting version is November 2024 SR2.&lt;BR /&gt;I've already submitted a case with Qlik Support.&lt;BR /&gt;Has anyone else experienced this issue and found a resolution?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 04:23:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2533873#M2594</guid>
      <dc:creator>Amarender</dc:creator>
      <dc:date>2025-10-21T04:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Alerting on Windows – Bug Summary (New Issues &amp; SSO Fix Recap)</title>
      <link>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2533874#M2595</link>
      <description>&lt;P&gt;Thank you for doing what I should have done.&lt;BR /&gt;Looking at it again, the 2024 Nov sr2 version seems completely unusable.&lt;BR /&gt;This is because it's a version that absolutely cannot be used without modification on sites that change operating ports or use virtual proxies.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 21 Oct 2025 04:34:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Reporting-Service-Alerting/Qlik-Alerting-on-Windows-Bug-Summary-New-Issues-amp-SSO-Fix/m-p/2533874#M2595</guid>
      <dc:creator>zolbae</dc:creator>
      <dc:date>2025-10-21T04:34:37Z</dc:date>
    </item>
  </channel>
</rss>

