Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Aug 28, 2023 3:10:02 AM
Jul 26, 2012 6:36:29 PM
Before reading this, please refer to the official QlikView Authentication - Qlik Online Help and your specific version for details.
QlikView allows for several 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.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.
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. It references http://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 also refers to 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.
Is there any update available how this would / should work with the current QlikView version?
Or has nothing changed since 2012 🤔?
MFA/2FA is becoming more and more requested, although setting it up in a Qlik Sense environment is easier QlikView remains a black box to setup.
I understand there can be several way's to implement, Qlik should offer some real life setup examples to help everybody to get forward getting security to a higher level.
Hello @p_verkooijen
General and up to date information is available on the Help - though specific customizations would need to be discussed with our Professional Services team.
This example is provided as-is.
I will check with our implementation SMEs though to see if we have any detailed examples in the pipeline.
All the best,
Sonja
Hello again @p_verkooijen
Ran this be our SME 🙂
The document is still valid. Not much has changed in QlikView. As for MFA/2FA: QlikView does not have any settings in the product to be modified to enable or work with MFA/2FA. Everything on this end would need to be set up and handled outside of the Qlik Platform with custom code or by your Identity Provider, which is what our Professional Services can assist with.
All the best,
Sonja
@Sonja_Bauernfeind thank you for the inquiries and information so far.
It looks like WebTicket doesn't work with the OCX api.
For example the AxQlikOCXLib.OpenDocumentEx method
if you pass the name of the document in the format qvp://{host}/{document_name}?webticket={webticket} then the document will not open and will return NULL.
Previously, it worked with a regular ticket and the document name in te format qvp://{host}/{document_name}?ticket={ticket} .
@Sonja_Bauernfeind Is there any specific documentation available for Azure AD Integration with QlikView?
Hello @Suraj_Maraje
Qlik doesn't have an out of the box tutorial for QlikView and Azure AD. We do have one for Qlik Sense.
I would recommend posting your query in the QlikView Integration forums - or, if you require direct assistance, reaching out to our professional services.
All the best,
Sonja
@Sonja_Bauernfeind Thank you so much!!