Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
aniketvasadkar_eq
Contributor III
Contributor III

Users from different domains are not ale to login to Qlik Sense

Hi All,

We have installed QlikSense Windows enterprise on Windows server 2019 standard.

Our server is in domain A and have added user directory connectors for A, b, c & D

We observed , users from domains B, C & D are not able to login to Qlik Sense. Domain A user is able to login.

Even Username password used are correct, QlikSense just says "User cannot be authenticated DOMAIN\Username"

I can able to connect to all domains via user directory connectors and able to to fetch users and view them on screen.

 

Thanks

Aniket

1 Solution

Accepted Solutions
aniketvasadkar_eq
Contributor III
Contributor III
Author

Hi @KhushbooManwani ,

Yes, we were able to fix this issue.

Qlik Sense uses Windows integrated authentication to authenticate users.

At DNS level, by default windows apply DNS suffix. So we need add additional DNS suffixes for login domains it is failing.

Under "Control Panel\Network and Internet\Network Connections"

1. Double Click on Ethernet 

2. Select Internet protocol version (TCP/IPv4)

3. Hit properties

4. Hit Advanced

5. Under DNS tab, you get option to append DNS suffix in order

Note: Your Windows Admin or IT Admin may help you to fix this quickly.

 

Thanks

Aniket

 

 

View solution in original post

11 Replies
Seanog_Murphy
Creator III
Creator III

Hi @aniketvasadkar_eq,

Perhaps the following video will be helpful
https://www.youtube.com/watch?v=SGm1eJKqFGo


aniketvasadkar_eq
Contributor III
Contributor III
Author

@Seanog_Murphy Thanks for the response

We are able to fetch users from different active directories by configuring user directory connectors.

Even this works in old system  but after we installed Nov 2021 version new windows servers it is not allowing users from other domain. 

Do we need any other configuration changes as configuration between old and new is same..

Thanks

Aniket

Seanog_Murphy
Creator III
Creator III

Hi @aniketvasadkar_eq,

Please ensure that domain trust has been setup. To the best of my knowledge, there should not be any difference between the Nov2021 and previous versions. 

aniketvasadkar_eq
Contributor III
Contributor III
Author

@Seanog_Murphy 

Yes two way trust between these domains already exists, as we are operating in same network with new server only

Seanog_Murphy
Creator III
Creator III

Hi @aniketvasadkar_eq,

Can you let me know if all users from all domains are sync'd in the QMC once you perform the UDC sync?

Perhaps it would be helpful to raise a case with support so that we can take a closer look
https://community.qlik.com/t5/Knowledge/How-to-create-a-case-and-contact-Qlik-Support/ta-p/1710992

aniketvasadkar_eq
Contributor III
Contributor III
Author

Hi @Seanog_Murphy 

UDC sync works fine without any issue. I can see all users from all domains.

When user tries to login from these affected domains we get warn message as below and authentication fails

System.Proxy.Proxy.DefaultModules.Authentication.FormAuthenticationRequestHandler 159 f852a62e-c200-41e7-8eff-2daa5f161847 DOMAIN\SERVICE_USER Could not retrieve domain name The LDAP server is unavailable.↵↓The server could not be contacted. at System.DirectoryServices.Protocols.LdapConnection.Connect()↵↓ at System.DirectoryServices.Protocols.LdapConnection.SendRequestHelper(DirectoryRequest request, Int32& messageID)↵↓ at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)↵↓ at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties)↵↓ at System.DirectoryServices.AccountManagement.PrincipalContext.ReadServerConfig(String serverName, ServerProperties& properties)↵↓ at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval()↵↓ at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password)↵↓ at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name)↵↓ at Proxy.DefaultModules.Authentication.FormAuthenticationRequestHandler.PerformAuthentication(HttpListenerContext context, BaseUser user, String password) f852a62e-c200-41e7-8eff-2daa5f161847
4792

 

Thanks

Aniket

 

Seanog_Murphy
Creator III
Creator III

Hi @aniketvasadkar_eq 

I suspect it is a permissions issue, but I think it would be best to raise a case with support to have a closer look

KhushbooManwani
Partner - Contributor
Partner - Contributor

Hi @aniketvasadkar_eq - We are also facing this issue for few days now. Did you manage to find any resolution for this ?

aniketvasadkar_eq
Contributor III
Contributor III
Author

Hi @KhushbooManwani ,

Yes, we were able to fix this issue.

Qlik Sense uses Windows integrated authentication to authenticate users.

At DNS level, by default windows apply DNS suffix. So we need add additional DNS suffixes for login domains it is failing.

Under "Control Panel\Network and Internet\Network Connections"

1. Double Click on Ethernet 

2. Select Internet protocol version (TCP/IPv4)

3. Hit properties

4. Hit Advanced

5. Under DNS tab, you get option to append DNS suffix in order

Note: Your Windows Admin or IT Admin may help you to fix this quickly.

 

Thanks

Aniket