Alternative Authentication and Authorization Methods

Enabling HTTP header authentication

HTTP header authentication allows a third-party service, for example Apache Web Server, to perform an authentication—using whatever mechanism it chooses—and then pass the username through to QlikView by injecting an HTTP header into the packet being sent to AccessPoint.

To enable this, we need to reconfigure the AccessPoint authentication:

In QMC, click on the System tab, expand QlikView Web Servers, and then select your web server. Click on the Authentication tab.
Set the Authentication option to Login, set the Type to Header, and set Login Address to Alternate login page (web form). The Header Name parameter, which defaults to QVUSER, is the name of the HTTP header that needs to be injected. The Prefix parameter should match one of the DSP names established earlier—for example, CUSTOM\ or LDAP\). Click on Apply.
The next step is dependent on your third-party product. For Apache, you would edit the httpd.conf file to include proxy and reverse proxy entries...

Tech Concepts

Programming languages

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

QlikView Server and Publisher

By : Stephen Redmond

QlikView Server and Publisher

By: Stephen Redmond

Overview of this book

Enabling HTTP header authentication

QlikView Server and Publisher

By : Stephen Redmond

QlikView Server and Publisher

By: Stephen Redmond

Overview of this book

Enabling HTTP header authentication

Confirmation

Buy this book with your credits?

Submit Your Feedback

Create a Free Account To Continue Reading

Sign in to activate your 7-day free access