Discussion Board for collaboration related to QlikView Deployment.
We are currently using a separate authentication application (called Tivoli) to authenticate the user credentials and pass that information on to the Qlikview server in the http header.
Once the user has logged in, we allow for dynamic license assignment and so a license gets assigned to that user. The actual license name looks like this: TIVOLI\MDAMIANO
The problem arises when a user needs to borrow a license from the server for development purposes (or to open a file created by another user) , by doing File-> Open In server. The only way this seems to work is when we use the NT Identity, which then assigns another license to that user based on the domain. So 1 user can consume 2 licenses which is not ideal.
I though the Alternate Identity should allow me to enter my existing Tivoli user name which already has a license assigned to it, but it doesn't work. When I enter my Tivoli user name and choose Alternate Identity, the software seems to connect to the server, but after opening a file from the server, it still shows 'Personal Edition'.
The string I am entering in the" connect to server" box is:
Any help/ideas would be appreciated!
I tried this - now I am getting an error saying:
" Failed to reach Server...
Switching to HTTP tunneling...
Connected to server OK, Negotiations Timed Out"..
Do you have a Small Business Server license or an Enterprise Server? In the second case, are you using DMS? Are the licenses assigned to Tivoli users Document CALs or User CALs? How are they getting to the server (ajax, IE Plugin, Desktop & Open in server...)
EDIT: In addition to the above, what does OSUser() and QVUser() return when you access a document via Tivoli?
we have the Enterprise Edition, DMS set up, and the licenses are User CALs.
The users get to the Qlikview files via AccessPoint/AJAX, after logging in thru Tivoli. That part seems to be working OK.
Some of the users are more of "power users" if you will, and they have the software installed on their PC. We want them to be able to borrow a license from the server by doing the File-> Open In Server option, and that is where the issue is. Since they have a license assigned to them in QEMC, you would think that they should be able to borrow a license from the server via the full client?
How do I find out what OSUser() and QVUser() return? Are these functions I should have in the document?
Thanks for your help, Maria
During Connectivity, Pleae check whether user log in through same domain or not.
also check port 4747 of qlikview server is accessible in the system in which you are getting error.
Check Port By following.
telnet IP_address PortNO
In regards to OSUser() and QVUser(), you can set them in a textbox just to confirm that the information is correct (active directory credentials in case of OSUser() and section access QVUser())
Any user with a user CAL should be able to borrow a license, but what seems the problem here is how the credentials are passed on to the server, and how the users get to the document (which is returned by QVUser()).
But yes, using Alternate Identity should work.
did anyone solve the problem?
We are faced with the same problem. License lease from Server via QikView Client works with NT-Identity but not with Custom User Identity. So that might not be a port issue, I think.
Security is set to DMS-Mode. When user logs in via the AccessPoint, everything works fine with Custom Users.
As far as I know, it's not possible to authenticate via the ticket method when using QV Desktop or QV Developer. My suggestion is that you try to install the QV Plugin and try to authenticate and open a document (with QV Plugin) via accesspoint, using the ticket authentication (Custom User Identity) system. If you do, I think the plugin will lease a license that will also work for your local QV Desktop or QV Developer as well. Not sure it works though, but worth a try!
if you get solution of following probelm , pls share.
"The problem arises when a user needs to borrow a license from the server for development purposes (or to open a file created by another user) , by doing File-> Open In server. The only way this seems to work is when we use the NT Identity, which then assigns another license to that user based on the domain. So 1 user can consume 2 licenses which is not ideal."