Skip to main content

Integration, Extension & APIs

Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.

Skip the ticket, Chat with Qlik Support instead for instant assistance.
Showing results for 
Search instead for 
Did you mean: 
Partner - Contributor III
Partner - Contributor III

Login screen for Mobile in a remote server mashup

Hi everyone,

I'm working on a qliksense mashup in a remote server.

I load the app objects on javascript file by API methods and I put it in my html file. The require.config is this:

var config = {

  host: "myIP",

  prefix: "/",

  port: "80",


require.config( {

  baseUrl: "http://"+ + (config.port ? ":" + config.port: "") + config.prefix + "resources"

} );

To pick the qlik js and css resources I'm conect to my Qliksense server

    <link rel="stylesheet" href="http://myserverurl:80/resources/autogenerated/qlikui.css">

    <link rel="stylesheet" href="http://myserverurl:80/resources/assets/client/client.css" media="all">

    <script src="http://myserverurl:80/resources/assets/external/requirejs/require.js"></script>

    <script src="/js/index.js"></script>

Ok, I put the app objects in my html file. When I enter in my webpage(mashup) with a pc (google chrome,firefox,etc.). The windows login screen appears, I write my user and pass and the app objects are loaded.

When I try it with an IOS or Android device the objects don't show neither the login screen, only the other html elements.

As a rule, when I enter to the hub or a qliksense app the qlik login screen appears instead windows login screen.
I try to do the same mashup app in a qliksense server and when I enter to the URL http://qliksenseserverURL/extensions/mashup/mashup.html ‌with my mobile device the qliklogin screen appears but when I do with the remote server app with the settings I have told no.

Any suggestions that I'm forget?


2 Replies
Partner - Contributor
Partner - Contributor

Hi Eric, did you manage to solve this issue? I have the same issue here.


Since you are not authenticated the <script> tags loading resources from behind the proxy will fail.

The <script> tag can't redirect the entire page hence the script entry point fails to load.

A quick and dirty fix to the problem is to upload a page as a extension similar to this: enigma.js/redirect.html at master · qlik-oss/enigma.js · GitHub

So instead of accessing your page a user would navigate to the redirect dummy page behind the proxy, authentication kicks in and you are re-directed to your authentication module. After authentication you are re-directed to the dummy page which in turn re-directs you back to whatever external page you define.