Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a question about the QlikView IE Plugin and SSL. I am using QlikView 9 on windows server 2008 with IIS 7 and I can get the access point set-up and working fine via https, except when using the IE plugin. A message pops up and asks if I "only want to display content that was delivered securely ;" if I choose "Yes" nothing is displayed, and if I choose "No" the application loads fine, but, I assume (perhaps incorrectly), that the connection is no longer secure. I do not experience any issue when using the Java or AJAX clients, however. In the config.xml file, I set "Always Tunnel" to "True," and I edited the "opendoc.js" file to "tunnel = https" rather than the default of "tunnel = http."
Again, I'm not sure what I am missing here, as https tunneling is working until I try to open an application using the plugin. If anybody has an idea, needs more informations, or knows what I need to change, please let me know.
Thanks,
Adam
Hi Adam,
To get rid of the prompt about unsecure content, rename opendoc.htm in the QvPlugin-folder to opendoc.bck. Then rename opendoc_fix.htm to opendoc.htm.
A good tool to verify if you're connecting using http or https is Fiddler ( http://www.fiddler2.com/fiddler2/ )
Hi Adam,
To get rid of the prompt about unsecure content, rename opendoc.htm in the QvPlugin-folder to opendoc.bck. Then rename opendoc_fix.htm to opendoc.htm.
A good tool to verify if you're connecting using http or https is Fiddler ( http://www.fiddler2.com/fiddler2/ )
Hi Bjorn,
Thanks for the reply, but when I tried that method it just resulted in a 404 error after I logged in to the access point and tried to open one of the applications. Could this be from a bad IIS configuration? Other than the handful of changes that have to be made to actually use IIS with QlikView, it is a standard set-up.
Thanks for the Fiddler tip, by the way; it shows that I am, in fact, connecting via https, and is a lot easier to use than a few other tools I have tried since I originally posted my question.
Adam
You get a 404-error? That's weird...you're sure that you renamed the opendoc_fix.htm to opendoc.htm and nothing else? If you opened it in notepad, make sure you didn't save it with a txt-extension, like opendoc.htm.txt. You should be able to right-click on the file in IIS Management Console and select "Browse..." without any 404-error (File not found).
opendoc_fix.htm is quite similar to the original opendoc.htm. The difference is that original opendoc.htm will open plugin using a frameset, while opendoc_fix.htm will utilize the classid of the active-x component.
I just tried it again and it seems to be working. I looked through my deleted files ( I had switched back to the original configuration after the 404 error) and saw that 'opendoc_fix' had been renamed 'opendoc.htm.htm,' so it was user error, which doesn't surprise me. Thanks for the help, and for tolerating my inexperience, both are very much appreciated.
Glad to hear you got it sorted out.
The above happens to me as well every now and then (I have no idea why Microsoft thinks it's a good idea to hide extensions for known file types, especially not on a server OS)
For tunneling, you also need to edit opendoc.js and change http to https:
if (tunnel != null) {
tunnel = tunnel[1];
if (tunnel == "") {
tunnel = 'http';
}
}
Thanks Bjorn .. your answers are very welcome!
Hi Mark,
You don't need to do that anymore. It has been changed.