Third party authentication

Anonymous — Wed, 25 Nov 2020 16:16:04 GMT

Hi guys,

I have a webapp with its authentication mechanism, now inside this webapp I created an area with my qlikview file and I manage this situation through iframe.

But I discovered that solution brings username and password, put them inside the header and sends to QVS.

In my opinion this kind of solution isn't correct, and browsers like chrome or opera think the same things, beacuse they don't let me see my qlikview file.

Now, maybe I made some mistakes or maybe there are better solutions, so can you help me to understand how can I improve my solution?

I read about CORS, can I use this mechanism in qlikview?

Thank to all

topic Third party authentication in QlikView

Third party authentication