Starting 1st of July 2020 Qlik Sense Desktop (QSD) can only be used if authenticated against Qlik Sense Enterprise (QSE) server with user access.
In our organization, the QSE installation is inside the internal network and, because of network policy, it cannot be exposed to public.
Thus, QSD cannot be used outside our network, whereas, we are expressly interested in using it outside our network!
Please note that the use cases in which we can benefit of Qlik Sense Desktop instead of the corporate client-server Qlik are indeed “outside office” situations where the connection to our corporate VPN is difficult or inconvenient.
Sometimes, further than “outside office” we have even “off-line” situations (while travelling, or in countries or contexts without sufficient band, etc..) so that we may just count on a minimal internet availability to authenticate at the beginning.
We are indeed strongly convinced that the new policy of allowing QSD for Qlik Customers makes sense exactly in these kind of situations.
Idea: A functionality for generating an offline "token" or "access pass" valid for 1 week on your Qlik Sense Enterprise server and then use this signed token as a way of authentication for QSD without actually having to connect to the Enterprise server. We can say that this is useful for people using QSD in airplanes or with devices that are not able to establish a connection to internal servers of the organisation.
What I am asking here is to be able to generate an unlock file, just like the one you can get at the branch, but linked to your corporate licence. You log into your Qlik server, you click a button and download an unlock file or some sort of token valid for a period of time.
Our Qlik server is unreachable from outside and that will not change. I'm not able to validate using the authentication link even once. That's why I'm asking for a solution that works without any need of connection to the server.
So, to summarize, no. What I requested hasn't been "delivered". I would like to kindly ask you to reopen the petition.
@cjgorrin , what you described is exactly the situation I have: my Qlik server is unreachable from outside and that can't be changed.
So far, I've bypassed this problem by downloading temporary unlock files form Qlik Branch, however depending on it is not ideal. Especially when have several Qlik Server instances we could be using to authenticate.
We understand that the network configuration of your server is not ideal for the authentication of the Qlik Sense Desktop. Currently, we don't have plans to generate an alternative form of unlocking QSD, other than the existing ones you already mentioned.
Hi @Caique_Zaniolo , it's a pity that there are no plans to address this at this moment. However, can we leave the idea open with the description provided by @cjgorrin ?
Looks like it stayed marked as "Delivered" by mistake.
I understand you currently have no plans to implement this feature, but... Isn't that what ideas here are for? To propose things that are not available but we -as users- want?
I think marking the idea as delivered is wrong because what we are asking hasn't been delivered. It should be left open and, at some point in the future, either implemented or discarded.
Hi all, just to explain the status change, the inital response from Caique defines the idea as delivered using authentication in QSD, and that there are no further plans to generate an alternative form other than the existing. Therefore if the status were to change it would be not planned or partially delivered. @cjgorrin@morenoju
Thank you for the explanation. However, I think what we are asking here has not been implemented yet, so it should not be marked as "delivered".
We are asking for the possibility of generating an "unlock file" like the one from the Qlik garden, but generating it from our own Qlik Sense server. This way, people would be covered by our licence even if they cannot establish a connection between QSD and the Qlik Sense server (air-gapped devices for sensitive data, no VPN, a long flight, etc.).
I think if there are no plans to implement this in the future (so far), it is better to leave the idea as open. Maybe more people will ask for it and you could consider implementing it at some point.
I still think that marking it as "delivered" makes people believe that what we are asking has been implemented, which is not true.
Thanks a lot for your explanation, your time and your kindness.
