topic Re: Mashup API context in Integration, Extension & APIs

Re: Mashup API context

Mon, 08 Jun 2015 10:48:04 GMT

Hi, ewg‌

We are currently using Qlik Sense 1.1 and perhaps something have changed since version 1.0 but we are running into following issue:

We want to pull Qlik Sense objects from our remote web site using Mashup API but are getting the following 403 error when opening an app:

From what I understand CORS has nothing to do with it since websockets are not restrained by the same origin policy. and also other files like qlik.js, client.js were loaded without any problems. So it must be the Qlik Sense server that enforces the origin policy.

So the question is: is there a way to allow origin on the server, so the handshake is carried successfully?

Re: Mashup API context

ErikWetterberg — Mon, 08 Jun 2015 11:29:58 GMT

Hi Rustam,

from the screenshot it looks like you are using ws:, should probably be wss:

Check out the config object, usually in the beginning of the javascript file:

var config = {
   host: window.location.hostname,
   prefix: prefix,
   port: window.location.port,
   isSecure: window.location.protocol === "https:"

};

Try setting isSecure to true.

Erik

Re: Mashup API context

Mon, 08 Jun 2015 11:43:19 GMT

Thanks for the answer, Erik!

Same error unfortunately

I've also tried adding client host to the websocket origin white list with no success either...

Re: Mashup API context

Alexander_Thor — Mon, 08 Jun 2015 14:22:33 GMT

Try just allowing rustam-pc.cl.local alternatively you could add localhost to your white list and try browsing your website from localhost:3000 and see if it helps.

Edit: Also it looks like you are running a virtual proxy so make sure you are setting the whitelist for the correct proxy.
Btw it looks like you are getting dual session cookies also, are you sure that you are setting the correct prefix?

Re: Mashup API context

Mon, 08 Jun 2015 14:41:44 GMT

Thanks, Alexander!

Allowing domain without port number did the job.