Expert Services
Qlikview Accesspoint Single Sign On
Version: 2健脾去湿汤
Date: 2010-11-15
Author(s)
QV9, QV10 IR
”A best practice is a technique or methodology that, through experience and rearch, has proven to reliably lead to a desired result.”
Contents
1Introduction (3)
topic是什么意思鲜为人知什么意思
1.1Example (3)
2Configuration QV Server (5)
2.1QVS DMS Mode (5)
2.2Configure Accesspoint (7)
新闻的时效性2.2.1Qlikview 9 (7)
2.2.2Qlikview 10 (8)
2.3Stop QlikView WebServer (10)
文件的含义3Configuration IIS (11)
3.1Install with IIS Support (11)
3.2Configure QlikView Server to u IIS (12)
3.3Create ur for Application Pool (13)
3.4Setup Application Pool (14)
3.5Ur Fiddler to test configuration (16)
3.6Summary (17)
4Configuration SSO-Example (18)一次性纸杯手工
4.1Logon site (19)
4.2Isapi-filter (20)
4.3Test Example (21)
1 Introduction
There are many single sign-on solutions in the market that protect a URL or web resource by redirecting the initial request for a protected resource to a login page prompting the ur to enter their (single sign-on) credentials. Once a ur is authenticated the ur is again redirected, this time back to the originally requested resource, and this time the Single Sign-on solution will have also ap
pended an HTTP header containing the ur id of the logged in ur. The name of the header will vary from system to system (e.g. the header name is “sm_ur” for SiteMinder, ivur for WebSEAL) and the content will be the ur id. If the Accesspoint does not find the ur id in the header, the “Login address” will have Accesspoint redirect to the given URL (note in most commercial single sign-on solutions like this the redirect is handled outside of Accesspoint by the SSO piece so in many cas this will simply be a precaution that should never really get called)
This document describes how to configure Qlikview with IIS to u the existing SSO infrastructure. In the following chapter we will also mimic a SSO infrastructure. Be aware, that this example configuration is for testing only, and is not meant to be deployed in a productive environment.
1.1 Example
Attached to this document you will find the sources for a small example to mimic a SSO infrastructure.
The provided logon site will handle the logon. The actual site will not check the password, but allow whatever urname you type in there. In a real world scenario, password checks etc. will have to be implemented.木瓜牛奶汤
The logon site will add a cookie to the ur called QvCookie, containing the urname in clear text. In a real world scenario this should be done using some kind of advanced ticket handling instead.
The ur will be redirected to the Accesspoint. The ISAPI filter will now check for this cookie and if it is found, it will transfer the value to the header, named QVUSER.
The Accesspoint will trust this header and request files from the Qlikview rver for this ur.
To allow us to u non windows-ur with Qlikview the Qlikview Server has run in DMS mode. Additionally as we have to configure the Accesspoint to look for the HTTP-Header field. As we want to deploy an ISAPI-Filter for the SSO Example, we then need to configure IIS.
2 Configuration QV Server
Out of the box Qlikview Server us Active Directory urs in NTFS mode. Typically a SSO system is placed on top of a non-AD directory rvices. In such a scenario the Qlikview Server needs to run in the so called “DMS”-mode and controls Authorization by itlf
(.a files typically managed by Qlikview Publisher).
2.1 QVS DMS Mode
U the QlikView Enterpri Management Console to configure DMS mode. Go to “System|Setup|QlikView Servers| Security|DMS Authorization”. Click “Apply” and restart the Qlikview rver. The screenshot slightly differ in QV9 and QV10. But the relevant tting is the same.
业务部岗位职责
