I've developed an application that for 10 users. The application access qvd files when we hit reload button. We dont have QlikVIew server so we have installed 10 QlikIVew desktop locally at the users computers.
Now what we want is to put QVD files on the virtual server so that we dont have to copy those qvd files locally at the users computer. This works fine without putting username and password to the virtual machine. But as soon as we protect the virtual machine with a username and password as the data qvd files are containing is very sensitive, the application wont load!
I've attached a picture showing what we are trying to achieve.
Can any one please help me how to access the QVD file from the virtual server when the virtual server is password protected?
I'm afraid that wouldn't solve the problem. We need to secure the server with a user ID and Password so that no body would have access to the server. but at the same time we need to reload our application using the qvds that are residing in a password protected server!
Why not schedule a windows task to reload a single qlikview from the command line then have the users pick up the qvw from there but...
If the QVW is stored locally on the users' machine how do you ensure the security of those workstations. If they are laptops I think you'd be in a bigger bind if security is that important. In the QVW the data is translated and structured for use while a QVD would require some knowledge to use, so it is unlikely that you will have somebody looking at a QVD simply out of curiosity
Bottom line, if security is so important your should just buy the server, SBE is very affordable and probably would cost you less in the long run, savings in Risk and Effort would be very valulabe.
I would suggest setting up an odbc connection on each laptop and then connect to it in your load scripts. It will pass an encrypted username/password along that the users won't be prompted for when they hit reload (it is stored in the load script as an encrypted string so it is not easily identified).
Then rather than pre-generate the qvd files for the users, connect them to the database and pull the data directly to their laptops. This can further restrict their access to the data based on their security levels in the database.
Downside is it will increase each individual users load times. As mentioned previously, SBE is well worth the investment if you can talk the powers that be into it.