Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
bkilicli
Partner - Contributor III
Partner - Contributor III

Domain Users and Workgroup Server

Hi Everyone,

Our Qlikview server in a WorkGroup but users in a domain. Is there any chance to login domain users to Access Point ?

When I try to login with Domain Users, Access Point redirect to login page without any error.

I can listing users from Active Directory in QMC > User Management Tab.

users qmc.png

ldap.png

Directory Service Connector Log

20180508T112134.667+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Looking up RootDSE: LDAP://192.168.0.16:389/RootDSE

20180508T112134.680+0300 Warning (ActiveDirectory.ActiveDirectoryProvider+CachedDirectoryEntryHolder) Fetching directoryentry LDAP://192.168.0.16:389/RootDSE failed: The user name or password is incorrect.

20180508T112134.680+0300 Warning (ActiveDirectory.ActiveDirectoryProvider) Exception while initializing LDAP://192.168.0.16:389: Setting up connection failed; The user name or password is incorrect.

20180508T112134.680+0300 Error (DSC.DirectoryFramework) setup path not successful for user 'egebant\dataqlik' at 'LDAP://192.168.0.16:389': System.Exception: Setting up connection failed; The user name or password is incorrect. ||  ||    at ActiveDirectory.ActiveDirectoryProvider.CachedDirectoryEntryHolder.get_Entry() ||    at ActiveDirectory.ActiveDirectoryProvider.CachedDirectoryEntryHolder..ctor(String _path, String _username, String _password, LogMessage _logger) ||    at ActiveDirectory.ActiveDirectoryProvider.SetupPath(String _path, String _username, String _password) ||    at DSC.DirectoryFramework.SetupResource(Guid id, String type, String path, String username, String password, IDictionary`2 newSettings)

20180508T112134.680+0300 Warning (DSC.DirectoryFramework) Setting up adDSP 'LDAP://192.168.0.16:389' wasn't successful: Setting up connection failed; The user name or password is incorrect.

20180508T112141.427+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Looking up RootDSE: LDAP://192.168.0.16:389/RootDSE

20180508T112141.434+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Looking up node: LDAP://192.168.0.16:389/CN=Partitions,CN=Configuration,DC=egebant,DC=com,DC=tr

20180508T112141.450+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Finding nCName: DC=egebant,DC=com,DC=tr

20180508T112141.450+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Searching for netbiosname...

20180508T112141.451+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Search hit: LDAP://192.168.0.16:389/CN=EGEBANT,CN=Partitions,CN=Configuration,DC=egebant,DC=com,DC=tr with netbiosname egebant and ncname: dc=egebant,dc=com,dc=tr

20180508T112141.451+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Adding netbiosname egebant as primary domain qualifier

20180508T112146.564+0300 Information Start web service call CheckNames

20180508T112146.564+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Query: '(&(|(name=*)(sAMAccountName=*))(&(!(objectclass=computer))(objectGUID=*))(|(&(objectCategory=group)(groupType:1.2.840.113556.1.4.803:=2147483648))(|(objectClass=User)(objectClass=person))))'

20180508T112146.663+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Query completed - 327 hits

20180508T112146.694+0300 Warning (ActiveDirectory.ADItem) property name: name with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.694+0300 Warning (ActiveDirectory.ADItem) property name: objectclass with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.694+0300 Warning (ActiveDirectory.ADItem) property name: objectguid with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.694+0300 Warning (ActiveDirectory.ADItem) property name: mail with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.694+0300 Warning (ActiveDirectory.ADItem) property name: adspath with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.694+0300 Error (ActiveDirectory.ADItem) Failed to initialize node : Invalid DirectoryEntry (objectGUID/sAMAccountName)

20180508T112146.694+0300 Error (ActiveDirectory.ActiveDirectoryProvider) Node initialization exception: Invalid DirectoryEntry (objectGUID/sAMAccountName)

20180508T112146.710+0300 Warning (ActiveDirectory.ADItem) property name: name with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.710+0300 Warning (ActiveDirectory.ADItem) property name: objectclass with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.710+0300 Warning (ActiveDirectory.ADItem) property name: objectguid with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.710+0300 Warning (ActiveDirectory.ADItem) property name: mail with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.710+0300 Warning (ActiveDirectory.ADItem) property name: adspath with value: System.DirectoryServices.ResultPropertyValueCollection

20180508T112146.710+0300 Error (ActiveDirectory.ADItem) Failed to initialize node : Invalid DirectoryEntry (objectGUID/sAMAccountName)

20180508T112146.710+0300 Error (ActiveDirectory.ActiveDirectoryProvider) Node initialization exception: Invalid DirectoryEntry (objectGUID/sAMAccountName)

20180508T112146.758+0300 Information Start web service call ResolveGroups for user egebant\___VMware_Conv_SA___

20180508T112146.758+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Query: '(&(sAMAccountName=___VMware_Conv_SA___)(&(!(objectclass=computer))(objectGUID=*))(|(&(objectCategory=group)(groupType:1.2.840.113556.1.4.803:=2147483648))(|(objectClass=User)(objectClass=person))))'

20180508T112146.761+0300 Information (ActiveDirectory.ActiveDirectoryProvider) Query completed - 1 hits

20180508T112146.762+0300 Information (ActiveDirectory.ADItem) Looking up memberof for node ___VMware_Conv_SA___

20180508T112146.765+0300 Information (ActiveDirectory.ADItem) No memberof attribute found, aborting search

20180508T112146.765+0300 Information Resolved 0 groups for egebant\___VMware_Conv_SA___:

20180508T112155.948+0300 Warning Search: no match for qualifier EGEQLIKSRV found among resources

Thanks.

2 Solutions

Accepted Solutions
Chip_Matejowsky
Support
Support

In QMC > System > Setup > Directory Service Connectors > DSC@ > Active Directory, do you have the correct path to your AD as well as Username/Password with access to AD configured?

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!

View solution in original post

Peter_Cammaert
Partner - Champion III
Partner - Champion III

But you should first check what Chip suggested. The error messages point to a connection failure, meaning that the DSP cannot connect to your domain controller using the credentials provided (if any). The DSP may be able to offload some information and unable to get to other details that are required.

View solution in original post

4 Replies
Chip_Matejowsky
Support
Support

In QMC > System > Setup > Directory Service Connectors > DSC@ > Active Directory, do you have the correct path to your AD as well as Username/Password with access to AD configured?

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!
bkilicli
Partner - Contributor III
Partner - Contributor III
Author

Yes, username/password configuration was true.  We took back qlikview server to domain.

Thanks for reply.

Peter_Cammaert
Partner - Champion III
Partner - Champion III

Since the QlikView server will never recognise AD users by default (no SSO because not part of a domain), you may want to configure "Alternate Login Page" in QMC->System->Setup->QlikView Web Servers->Your Web Server->Authentication->Login Address. A login dialog cannot be avoided.

Peter_Cammaert
Partner - Champion III
Partner - Champion III

But you should first check what Chip suggested. The error messages point to a connection failure, meaning that the DSP cannot connect to your domain controller using the credentials provided (if any). The DSP may be able to offload some information and unable to get to other details that are required.