This how-to explains the steps required to add users and setup the QlikView Management Console to allow license leasing in DMS mode using custom users and custom user authentication.
A defect, ID QV-8818, has prevented this from working the following releases:
QlikView 11.20 SR15 and up
The defect was resolved in QlikView 12.20 IR (QlikView November 2017)
Create a user
In the QMC (QlikView Management Console) navigate to > System > Setup > Directory Service Connectors > DSC > Custom directory
, add a custom Path.
Tab Users, click on the green + button and create a new user “MyUser1
The user name is case sensitive
and thus will need to be entered the same way in AccessPoint.
Click on “Apply
” to validate the changes.
Switch to DMS mode
In QMC > System > Setup > QlikView Servers > QVS > Security > Authorization
and click on “Apply
Set up authentication
In QMC > System > Setup > QlikView Web Servers > QVS > Authentication
- Change Authentication Type from NTML to “Custom User”; leave “CUSTOM” as prefix.
- Change Login Address from “Default login page” to “Alternate login page”, this will allow you to enter an alternate user name for authentication.
Click on “Apply
” to validate the changes.
At this stage, you can test the connection with the AccessPoint
The AccessPoint is empty because the QMC has been switched to DMS; We have to configure manually which user can access which app.
Add an app to this user
In QMC > Documents > User Documents > “Any document” > Authorization
Grant access to MyUser1
Refresh the AccessPoint. The document should be displayed now.
Lease a license
Open the Desktop. If no license has already been leased, you will have the Personal Edition.
Now, let’s see what happens when we try to lease a license as usual with the “Open in Server
If you use the NT Identity, nothing will happen because QlikView will try to match your NT identity with the list of users you previously created. You can click on “Connect
”, but the list of applications remains empty.
If you use “Alternate Identity
” with “MyUser1
” or “Custom\MyUser1
” or “CUSTOM\MyUser1
” and click on connect, you will have a timeout message after a couple of seconds.
Connected to the server OK, No reply received
Switching to HTTP tunneling
Connected to server OK, Negotiations Timed Out
When opening in server, by default Qlik Desktop uses the qvp protocol on port 4747.
But the port 4747 is open.
And Qlik service is using this port.
This procedure is correct in NTFS
mode, not in DMS
Set up the Desktop
In Settings > User Preferences > Locations
Change “QlikView Server AccessPoint (URL)”
Change “Default License Lease Server (URL)”
Save and close this window.
Now, open the AccessPoint from your Desktop (Tools > Open QlikView AccessPoint
You will have the AccessPoint connection window.
You can see the application.
Open the app, you get a license!
After step 4 (adding an app to the user), I cannot see any document in the AccessPoint
- Double check that you have typed the same custom name in:
- System > Setup > DSC > Custom Directory > General > Path
- System > Setup > QVWS > Authentication > Parameters
If those 2 names don’t match, you won’t be able to see any documents.
At the very last step, I still don’t get a license, my desktop remains in personal edition
Does your LEF allow license leasing?
If so, which version are you using? This process was working fine in QlikView 11.20 SR 11 and SR12 but a bug QV-8818 has been found in QlikView 11.20 SR15 and in QlikView 12, which was addressed in the 12.20 IR release (QlikView November 2017)
Web Server and tunneling considerations
QlikView Web Server - There should be no need to configure anything when using the QlikView Web Server, and it will handle tunneling across the entire QlikView Server Cluster.
IIS/QlikView Settings Service - If TCP port 4747 is blocked between the clients and the QlikView server(s), and the IIS web server runs on a server that is not running the QlikView Server Service, there is a need to add the following settings to the Windows Registry on the IIS web server(s) and note that you may only specify one of the QlikView Server nodes in a cluster as well, so you will have to decide which QlikView Server node to use for tunneled connections. If you have multiple web servers and QlikView Servers, you can assign a different QlikView Server node to each IIS Web server in that case.
Windows Registry key addition required:
[HKEY_LOCAL_MACHINE\SOFTWARE\QlikTech\QlikTunnel] (You will likely have to create the 'Key', in particular QlikTunnel, as it is not likely going to be there.)
QVSPort=dword:000012a6 (This is a Dword Registry type where the Name field is populated with QVSPort, and the value is 4774 if you change the display to 'decimal' instead of 'hex', this can be easier to use.)
QVSServer=QvsHost (This is a String Value Registry type where QVSServer goes in the String Name field and the one of the QlikView Server names goes in the Value field, QvsHost represents that server name here, the value you input should be the actual server name.)
NOTE: IIS with QlikView Server Tunneling in a Clustered QlikView Server environment is NOT supported, only the QlikView Web Server supports a use case of clustered QlikView Servers, IIS and the need for tunneling when IIS resides on a different server.