User directory connectors ODBC properties
The following property groups are available for user directory connectors of the type ODBC.
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 ODBC connection properties in the Qlik Sense system.
Property | Description | Default value |
---|---|---|
User directory name | The name of the user directory. Must be unique, otherwise the connector will not be configured. | - |
Users table name | The name of the table containing the users. | - |
Attributes table name | The name of the table containing the attributes of the users. | - |
Visible connection string |
The visible part of the connection string that is used to connect to the data source. Information noteThe two connection strings are concatenated into a single connection string when making the connection to the database.
|
- |
Encrypted connection string |
The encrypted part of the connection string that is used to connect to the data source. Typically contains user name and password. Information noteThe two connection strings are concatenated into a single connection string when making the connection to the database.
|
- |
Synchronization timeout (seconds) | The timeout for reading data from the data source. | 240 |
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!