<?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 Sense April 2020 Upgrade Issue in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-April-2020-Upgrade-Issue/m-p/1722222#M16240</link>
    <description>&lt;P&gt;We have resolved the issue. Its more of a workaround than fix cuz its a Bug and will also open a ticket with Qlik. So what happened is in the Virtual Proxy in QS we had the Header name as "SM_USER" and in siteminder we had "SM_USER" and "SM_USERDN".&amp;nbsp; When we upgraded to April 2020Release it started looking for like a wild card anything starting with "SM_USER". That is why we were seeing 2 different UserID poppping up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We used another Hear name from Siteminder and that fixed the issue.&lt;/P&gt;</description>
    <pubDate>Thu, 25 Jun 2020 14:59:08 GMT</pubDate>
    <dc:creator>Rehan</dc:creator>
    <dc:date>2020-06-25T14:59:08Z</dc:date>
    <item>
      <title>Qlik Sense April 2020 Upgrade Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-April-2020-Upgrade-Issue/m-p/1721513#M16225</link>
      <description>&lt;P&gt;We were using Qlik Sense Nov 2019, single Node Dev environment. We are using Siteminder /IIS for Authentication. When users access qliksensedev URL they are prompted for the credentials by Siteminder and they get access to HUB. We upgraded to April 2020 release Patch 3 last Fri and noticed something Odd for userid's.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Now whenever the user is logging in it creates an additional entry for the user in QMC (Users) other&amp;nbsp; than the&amp;nbsp; original user id.&lt;/P&gt;&lt;P&gt;For example my original id is showing up as saeedr2 and another id shows up as soon as I log into Qlik Sense and that id is something like cn=saeedr2,ou..................................... (This Id is coming from Siteminder) cuz attached screenshot shows the Header SM_USERDN has the exact same entry.&lt;/P&gt;&lt;P&gt;Please see the attached screenshots.&lt;/P&gt;&lt;P&gt;Any idea&amp;nbsp; why the upgrade would have caused this and what the fix for this&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jun 2020 03:22:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-April-2020-Upgrade-Issue/m-p/1721513#M16225</guid>
      <dc:creator>Rehan</dc:creator>
      <dc:date>2020-06-24T03:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Sense April 2020 Upgrade Issue</title>
      <link>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-April-2020-Upgrade-Issue/m-p/1722222#M16240</link>
      <description>&lt;P&gt;We have resolved the issue. Its more of a workaround than fix cuz its a Bug and will also open a ticket with Qlik. So what happened is in the Virtual Proxy in QS we had the Header name as "SM_USER" and in siteminder we had "SM_USER" and "SM_USERDN".&amp;nbsp; When we upgraded to April 2020Release it started looking for like a wild card anything starting with "SM_USER". That is why we were seeing 2 different UserID poppping up.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We used another Hear name from Siteminder and that fixed the issue.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2020 14:59:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Qlik-Sense-April-2020-Upgrade-Issue/m-p/1722222#M16240</guid>
      <dc:creator>Rehan</dc:creator>
      <dc:date>2020-06-25T14:59:08Z</dc:date>
    </item>
  </channel>
</rss>

