Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
A ticket once created is valid for 2 minutes, if it is not used in that time it is destroyed
Once a ticket is used to establish a session it cannot be used again. Within that session a user can open several documents
A web ticket can be used to open a single document or the QlikView Access Point
Web Tickets can be used with features such as Clustering and Document chaining
To use web tickets there are two areas that need to be address The Code in your login page and the Server Configuration.
Qlik Support cannot offer direct assistance with coding a web ticket solution. The information provided in this article is given as-is and if assistance is required, please contact Qlik Professional services.
Option 1 – use windows permissions
Option 2 – use an IP address white list
Open the web server config file from C:\ProgramData\QlikTech\WebServer\config.xml
Locate the line <GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx" />
Replace it with the following specifying the IP address(s) of the web server(s) running the code
The function to request a ticket is a fairly simple HTTP post command which returns a ticket as a string, this method can be used by a wide range of technologies. The examples provided here use asp.net but it can easily be adapted for PHP, Java and others.
In its raw form the HTTP Post entry to the getwebticket.aspx page on the QlikView server looks like this:
<Global method="GetWebTicket"> <UserId>FRED</UserId> <GroupList><string></string></GroupList> <GroupsIsNames>true</GroupsIsNames> </Global>
The response containing the ticket should look like this: <Global><_retval_>ABC123XYZ567FGH456</_retval_></Global>
The above raw commands needs to be embedded into the code for the login form. The example provides no actual logic to authenticate the user against anything but provides the framework to add it in. The example takes the form of a simple login page asking for a user ID, password and optional groups, for cases where you already have the identity of the user then the UI from the example could be removed to give a seamless login from one system to another.
Once the login button is clicked there is a Login function that is called. This function in the example does nothing and always says the user is valid: here you would need to provide code to suit your environment, the example just trusts the entry automatically.
loginOK = ValidateUser(username, password);
Following user validation the next function makes the HTTP post to request a web ticket. The code requires the input of the URL of the QlikView server and in this case embeds a userid and password which has permissions to ask for a ticket (see notes on setting up QV trusts).
ticket = getTicket(username, groups, ticketinguser, ticketingpassword);
Once the ticket is returned, a URL is built and the user is redirected to either the access point or to a single document.
You should now be redirected to the QlikView AccessPoint and be logged in at the user specified in the form and see the documents that user is permitted to see.
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.