Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
GiuQlik
Partner - Contributor II
Partner - Contributor II

Problem synchronizing user directory connector

HI,
I ask the community for help with the problem I am facing.


1. I added new users, visible in QMC -> Users;
2. these users access the hub, but cannot see any Streams/Apps;
3. I tried to sync in the user connector directory, but...

I have this:

GiuQlik_1-1726558108776.png

and this:

GiuQlik_2-1726558135990.png

Can you help me?

 

Thank you

 

Labels (1)
1 Solution

Accepted Solutions
M_B
Creator
Creator

For the first one LDAP://domain:636/RootDSE, try using 389 instead (LDAP://domain:389).

If you would like to try to connect securely using port 636, try LDAPS://domain:636

Port 389 is for (LDAP) (non-secure) LDAP://domain:389

Port 636 is for (LDAPS) (secure) LDAPS://domain:636

View solution in original post

3 Replies
M_B
Creator
Creator

Can you try "LDAPS://domain"? Double check the password for the account and make sure the LDAP filter does not have any issues. I faced a lot of problems setting up LDAP and usually the filter would have something wrong.

Check this for some hints about building the filter:

LDAP Filter Cheat Sheet

Hope this helps.

GiuQlik
Partner - Contributor II
Partner - Contributor II
Author

thanks for the reply.

By doing the test you suggested, I eliminated the warning present in the second screen (and in the log). The refresh date updated, but the status remained in "Idle" and now the error is present in the log:

5 ERROR UserManagement.Repository.Repository.Users.Factories.UserDirectoryFactory Fetching directoryentry LDAP://anpal.local:636/RootDSE failed: The server is not operational.↵↓
6 ERROR UserManagement.Repository.Repository.Users.Factories.UserDirectoryFactory Exception while initializing LDAPS://anpal.local: Setting up connection to LDAP root node failed. Check log file.

M_B
Creator
Creator

For the first one LDAP://domain:636/RootDSE, try using 389 instead (LDAP://domain:389).

If you would like to try to connect securely using port 636, try LDAPS://domain:636

Port 389 is for (LDAP) (non-secure) LDAP://domain:389

Port 636 is for (LDAPS) (secure) LDAPS://domain:636