F -X C h a n ge

F -X C h a n ge

c u -tr a c k

N
y
bu
to
k
lic

3.3.

Key Components

3rd Party Login System

o
This could be the anything from an externally hosted customer web portal or based on the
same server the web server mentioned below. The key point is that they user has logged into
something and is a known user.
o
On a web page somewhere (such as on a portal) a link is placed to a launch page on the
QlikView web server with a scrambled user id passed as a parameter.
o

In this scenario the user clicks this link to begin the access to QlikView

A web server placed in the DMZ which is accessible from the internet

Hosts a web page that invisibly handles the ticketing process and launch of QlikView

Hosts the QlikView 9 Ajax Client and handles access to the QlikView document

QlikView 9 Server

Hosted internally permitting access to QlikView server from the web server only

Hosts a web service for issuing user tickets

o
QlikView Document Configured with section access based on the 3rd party user id (email
addresses)
3.4.

Process Flow

1.

User logs into customer web portal

2.

Web portal creates a link to QlikView and adds a scrambled user id on the link

E.g. http://QlikView.co.uk/launchqv.aspx?uid=hgvkjg4v2kgjv4r9na

NB the above URL is the external URL that addresses to the web server in the DMZ

3.

User clicks on the link to QlikView

4.

The web server extracts the user id from the URL

5.
The web server makes a web service call to the QlikView Server Ticketing Service to
request a user ticket for the logged on user

.d o

.c

.d o

lic

to

bu

O
W
!

PD

O
W
!

PD

c u -tr a c k

.c