QlikView allows for a number of 3rd party, custom authentication methods to be implemented, which may leverage an Identity Provider (IdP) of choice. However, many aspects of this integration is limited to best-effort support from Qlik Technical Support. See How and When to Contact the Consulting Team?
By default. QlikView only interacts with Windows using the appropriate APIs in the background, allowing Windows to carry out any authentication attempts and passing that information to the QlikView system. Custom Users in the Directory Service connector are a second option, which allows QlikView itself to do authentication.
Any other user repository will require external, 3rd party implementations.
! The information in this article is provided as-is and to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This document includes some possible examples in a QlikView 11 implementation of WebTickets and Header authentication, with examples from .NET, PHP, and LDAP integrations. The examples are provided as is.
! The document referenceshttp://localhost:4730/qtds.asmx, which was a valid URL used in QlikView 10 (no longer supported). This function has been removed in QlikView 11.
! The document references a WebTicket implementation limitation: A current limitation is that the QVWS or IIS used in steps 2 and 3 (i.e. the server you collect the ticker from and the server you redirect the user to) must be the same machine. This limitation no longer applies in the current QlikView 12 and 11.20 versions.