User directory connectors Active Directory properties
The following property groups are available for user directory connectors of the type Active Directory.
Identification
The Identification property group contains the basic UDC properties in the Qlik Sense system.
All fields are mandatory and must not be empty.
Property | Description |
---|---|
Name | The name of the UDC configuration defined from the QMC. |
Type |
The UDC type. |
User sync settings
The User sync settings property group contains the user sync properties for the user directory connector.
Property | Description | Default value |
---|---|---|
Fetch user data on first access, then keep in sync |
|
Selected |
Connection
The Connection property group contains the Active Directory connection properties in the Qlik Sense system.
Property | Description | Default value |
---|---|---|
Path | The URI used to connect to the AD domain. To support SSL, specify the protocol as LDAPS instead. | ldap://company.domain.com |
User name | The optional user ID used to connect to the AD server. If this is empty, the user running the Qlik Sense repository is used to log on to the AD server. | - |
Password | The optional password for the user above. | - |
Advanced
The Advanced property group contains the advanced Active Directory properties.
Property | Description | Default value |
---|---|---|
Additional LDAP Filter |
Used as the LDAP query to retrieve the users in the AD. | Blank |
Synchronization timeout (seconds) | The timeout for reading data from the data source. | 240 |
Page size of search |
Determines the number of posts retrieved when reading data from the data source. Tip note If the user synchronization is unsuccessful, try setting the value to no value.
|
2000 |
Tags
The Tags property group contains the available QMC tags in the Qlik Sense system.
Property | Description |
---|---|
Tags |
Tip noteIf no QMC tags are available, this property group is empty.
Connected QMC tags are displayed under the text box. |
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!