User directory connectors ODBC properties

Four ODBC options exist when creating a new user directory connector (UDC). They all have the same properties and fields, but for Access (via ODBC), Excel (via ODBC), SQL (via ODBC), and Teradata (via ODBC), some of the fields contain default values for support. You will most likely have to change those values.

备注: If you use a PostgreSQL database, and have table names with capital letters, or special characters, such as ".", you must enclose the table names with quotation marks. Without quotation marks, validation of the table names will result in an error. Examples of table names: "table.Name", public."Table" (or "Table"), testschema."Table".

The following property groups are available for ODBC UDC.

Identification

All fields are mandatory and must not be empty.

LDAP identification properties
Property Description
Name The name of the UDC configuration, defined from the QMC.
Type

The UDC type.

User sync settings

LDAP user sync properties
Property Description Default value
Sync user data for existing users
  • When selected, only the existing users are synchronized. An existing user is a user who has logged in to Qlik Sense and/or been previously synchronized from the configured directory service.
  • When not selected, all the users, defined by the properties for the UDC, are synchronized from the configured directory service. You can create a filter to Active Directory, ApacheDS, or Generic LDAP if you only want to synchronize a selection of users.
备注: The user attributes are only synced when a user logs in to the hub. Even if you delete the user in the QMC, the active session is still valid for the user that has been deleted. If the hub is only refreshed, the user is added to the database, but without any attributes.

Selected

Connection

备注: When loading .txt files using Microsoft Access Text Driver (*.txt, *.csv), you must use the connector type Access (via ODBC) instead of ODBC.
Property Description Default value
User directory name

The name of the user directory. Must be unique, otherwise the connector will not be configured. The name must not contain spaces.

-
Users table name The name of the table containing the users. Include the file extension in the table name, for example: Table.csv.
备注: When setting up an Oracle ODBC user directory connector, the Users table name and Attributes table name must be prefaced by the owner of those tables. For example: OWNER.USERS instead of only USERS.
-
Attributes table name The name of the table containing the user attributes. Include the file extension in the table name, for example: Table.csv.
备注: When setting up an Oracle ODBC user directory connector, the Users table name and Attributes table name must be prefaced by the owner of those tables. For example: OWNER.USERS instead of only USERS.
-
Visible connection string

The visible part of the connection string that is used to connect to the data source. Specify one of the following:

  • A full connection string, for example: Driver={SQL Server Native Client 11.0};Server=localhost;Database=Users;Trusted_Connection=yes;
    1. Driver must point to a driver currently on the machine. In the ODBC Data Source Administrator, check which driver to specify. Search for "data source" to find the application.
    2. Server must point to the server that you want to connect to.
    3. Database must point to the database where the tables are.
    4. Trusted_Connection=yes may be required, depending on the setup. In this example it is required.
  • A pointer to an established System DSN, for example, dsn=MyDSN;
备注: The 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, this string contains user name and password.

Example:  

Assume that you have a connection string as follows:

Driver={Microsoft Access Driver (.mdb)};Dbq=C:\mydatabase.mdb;Uid=Admin;Pwd=verySecretAdminPassword;

You do not want to store that connection string in the database as it is, because the secret password would then be visible to others. To protect the password, do the following:

Save the first part:

Driver={Microsoft Access Driver (.mdb)};Dbq=C:\mydatabase.mdb;

in the Visible connection string field, and the second part:

Uid=Admin;Pwd=verySecretAdminPassword;

in the Encrypted connection string field. The second part is then stored encrypted in the database and is not shown when you open the UDC again for editing.

备注: The 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

LDAP tags properties
Property Description
Tags
提示: If no tags are available, this property group is empty.

Connected tags are displayed under the text box.

See also: