Which QV version supports (non-ActiveDir) LDAP for Authentication
Which version (if any) will support using Configurable LDAP (or another LDAP setup in Directory Services Connector), notActiveDir, for QlikView authentication? If yes, how?
(I have internal QV servers setup to use ActiveDir for authentication, and NTFSfor file access. Those systems are working fine.)
I have an Amazon hosted QV instance that I need to use (Sun) LDAP directoriesservices for authentication (, and authorization?).
I’ve installed OpenDS onto my AWS QV instance, configured OpenDS it with objects andattributes, and a couple of test users (one real, one just for test). I don’t have the option to connect from AWSQV instance to my internal (Sun) LDAP directory server, so I expect to exportobjects/attributes to an LDIF file, zip it, use WinSCP to transport it to myAWS QV instance, un-zip it, then import the LDIF into OpenDS. That’s all working fine.
??? Which version of QV (v10 + patch? or v11) allows me to use LDAP (not ActiveDir) as myauthentication agent, and how would I use the existing LDAP objects/attrib (as shown in the picture) to setup QV toprovide user interrogation and authentication, much like ActiveDir does? And, no, I do not want to just query the LDAP from within QV, I want to use non-ActiveDir LDAP as my authentication source, and hopefully, to use it for authorizations as well.
I have seen the statement in the QV v10 Admin Ref concerning not being able touse Configurable LDAP for use in authentication, so maybe a later Service Patchdoes? Or QlikView v11 ?
I do have QV enterprise and Publisher, so I’ve got all the licensing I need. I've reviewed many (all) the various community discussions related to LDAP and DMS, but no working examples (not using ActiveDir). I've also pored over the QV Admin Ref Guides.
listing of LDIF from the OpenDS objects/attributes (via Apache Directory Studio) that aresetup and available on the AWS QV instance.
LDIFexport to CVS, including structural objects, etc…
Please remember that QlikView does not do authentication. Windows does that and pass the information to QlikView where it can do the authorization. If it is non-windows you are trying to authenticate against, you will have to write the code to do the authentication and pass the header information to QlikView for authorization.
Bill
Bill - Principal Technical Support Engineer at Qlik To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
.png "Former Employee"){kind=icon}
