<?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 External access in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/External-access/m-p/1115922#M19145</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wondering who else is in a situation like mine? We have clients who need to access our Qlik Sense applications and they are external to our organisation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we currently just use windows authentication on our AWS server so when we looked at Qlikview - it was simply a matter of using the extranet server version and creating the users on the box. With Qlik Sense a lot of the major corporates we deal with only allow port 80 or 443 for authentication. Getting their IT teams to change / allow port 4243 which Sense uses can be troublesome because they don't often have to do this for other products. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anyone else facing these kinds of issues or has faced and fixed it as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Aug 2016 12:10:04 GMT</pubDate>
    <dc:creator>mmonfort</dc:creator>
    <dc:date>2016-08-16T12:10:04Z</dc:date>
    <item>
      <title>External access</title>
      <link>https://community.qlik.com/t5/App-Development/External-access/m-p/1115922#M19145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wondering who else is in a situation like mine? We have clients who need to access our Qlik Sense applications and they are external to our organisation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now we currently just use windows authentication on our AWS server so when we looked at Qlikview - it was simply a matter of using the extranet server version and creating the users on the box. With Qlik Sense a lot of the major corporates we deal with only allow port 80 or 443 for authentication. Getting their IT teams to change / allow port 4243 which Sense uses can be troublesome because they don't often have to do this for other products. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is anyone else facing these kinds of issues or has faced and fixed it as well?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Aug 2016 12:10:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/External-access/m-p/1115922#M19145</guid>
      <dc:creator>mmonfort</dc:creator>
      <dc:date>2016-08-16T12:10:04Z</dc:date>
    </item>
  </channel>
</rss>

