<?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: REST API - Using different accounts in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306687#M1250404</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Robert. Yes, what I want to be able to do is use different credentials per session because this can affect the data returned. So when user A logs in, they may have permissions to see all of the data across all departments in a particular data set but when user B logs in, they may only see one department's data.&lt;BR /&gt;It seems that the connector is instantiated before any dynamic filtering can be applied but I hope I am wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Jun 2017 11:39:01 GMT</pubDate>
    <dc:creator>bearschoice</dc:creator>
    <dc:date>2017-06-03T11:39:01Z</dc:date>
    <item>
      <title>REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306684#M1250398</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My company's software has a REST API that requires login and depending on which account is used, different results will be returned to maintain confidentiality. Is it possible to set up a data connector so that it accepts username and password at run time and to load data at that point? If so, how is that done?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306684#M1250398</guid>
      <dc:creator>bearschoice</dc:creator>
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306685#M1250399</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Yes, the REST connector supports login credentials.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jun 2017 11:31:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306685#M1250399</guid>
      <dc:creator>RSvebeck</dc:creator>
      <dc:date>2017-06-03T11:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306686#M1250401</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Oh, I see you write "at runtime".... somthis all would depend on your setup... so you want a on-demand reload where the user credentials are transfered back to the qmc before reloading?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jun 2017 11:34:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306686#M1250401</guid>
      <dc:creator>RSvebeck</dc:creator>
      <dc:date>2017-06-03T11:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306687#M1250404</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Robert. Yes, what I want to be able to do is use different credentials per session because this can affect the data returned. So when user A logs in, they may have permissions to see all of the data across all departments in a particular data set but when user B logs in, they may only see one department's data.&lt;BR /&gt;It seems that the connector is instantiated before any dynamic filtering can be applied but I hope I am wrong.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jun 2017 11:39:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306687#M1250404</guid>
      <dc:creator>bearschoice</dc:creator>
      <dc:date>2017-06-03T11:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306688#M1250406</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;I see. In standard, data security settings is normally handled by Qlikview itself, and the Qlikview data layer normally contains all data.&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;The reasons are many but amongst the important ones ; we normally do not want to allow users to stress the source databases by the users demand.&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;Allowing users to trigger new database loads is not best practice as it can basically make users to lock the source databases. Perhaps not from a REST interface though, but they might be limited in # requests per day or such...&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;My recomendation is that you create a ETL standard QVD layer in your Qlikview installation and use the standard "section access" to make sure users gets the data &amp;nbsp;they are allowed to get.&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;What you describe as your need is however possible to do, but you would need to make a different QVW for each user... since the credentialls will be different for each user.&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Jun 2017 21:19:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306688#M1250406</guid>
      <dc:creator>RSvebeck</dc:creator>
      <dc:date>2017-06-03T21:19:07Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306689#M1250409</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Robert, not the answer I was hoping for but I understand the reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just a thought, we are using Qlik Sense but I presume the model is the same and so the solution will be the same.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Jun 2017 07:51:06 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306689#M1250409</guid>
      <dc:creator>bearschoice</dc:creator>
      <dc:date>2017-06-04T07:51:06Z</dc:date>
    </item>
    <item>
      <title>Re: REST API - Using different accounts</title>
      <link>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306690#M1250411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class=""&gt;Oh you are using sense. In that case I am not sure where the limits are. With the Sense QMC and Sense Extensions the possibilities increase alot.&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;Lets hope some Sense QMC expert finds this thread.&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;BR /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 04 Jun 2017 17:43:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/REST-API-Using-different-accounts/m-p/1306690#M1250411</guid>
      <dc:creator>RSvebeck</dc:creator>
      <dc:date>2017-06-04T17:43:25Z</dc:date>
    </item>
  </channel>
</rss>

