Chat now with support
Chat with Support

Quick Connect for Base Systems 2.4 - Release Notes

Known issues

The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.

 

Table 2: Known issues

Known issue

Issue ID

Quick Connect fails to support the provision, deprovision, and update operations from ActiveRoles Server to a delimited text file.

WORKAROUND

Contact technical support for more information on this issue.

48527

When using the Add Connected System Wizard to create a connection to Sun One Directory Server, you may encounter the following error on the "Specify connection settings for LDAP directory service" page: "The specified LDAP Directory service cannot be contacted. Details: One or more arguments are invalid."

WORKAROUND

  1. On the "Specify connection settings for LDAP directory service page" of the wizard, click "Advanced Options".
  2. In the Advanced dialog box, clear the "Force ADSI to use secure authentication" check box, and then click OK.
  3. Step through the wizard to complete the creation of the connection.

48530

Quick Connect may fail to synchronize some objects in the synchronization scope specified for a LDAP Directory Service.

WORKAROUND

  1. Open the following folder: <Quick Connect for Base Systems installation folder>\Service\Connectors\GenericLdapConnector\

    By default, the Quick Connect installation folder is %ProgramFiles%\Quest Software\ActiveRoles Quick Connect\Service\Connectors\GenericLdapConnector\

  2. Open the ConnectorConfig.xml file in Notepad.
  3. In the ConnectorConfig.xml file, replace the element "<SearchPageSize>0</SearchPageSize>" with "<SearchPageSize>1000</SearchPageSize>".
  4. Save changes to the file, and then rerun the synchronization step.

Note that this procedure does not apply to Sun One Directory Server.

48550

When attempting to provision objects from ActiveRoles Server to a data system connected through the Generic LDAP Connector, you may encounter the error message "The directory property cannot be found in the cache." This problem only occurs if no values are set for the UniqueID attributes defined for the target data system.

WORKAROUND

Configure attribute population rules for the UniqueID attributes:

  1. In the Quick Connect Administration Console, open the "Workflows" tab, and then open the tab for workflow that contains a link to the provisioning synchronization step where the problem occurred.
  2. Double-click that synchronization step.
  3. In the "Provisioning Step Settings" dialog box, open the "Provisioning Rules" tab, expand "Configure Initial Attributes Population Rules", and then use the

    "Attributes | Rule | Script | Text" split button to configure initial attribute population rules for UniqueID attributes.

  4. When you are finished, click OK to close the "Provisioning Step Settings" dialog box.
  5. Rerun the provisioning step.

54461

You may experience any of the following issues when running the provisioning or deprovisioning synchronization step:

  • Quick Connect may unexpectedly provision an object that has already been provisioned earlier.
  • Quick Connect may unexpectedly deprovision objects that do not meet the deprovisioning criteria.

These issues show up if you have configured attribute updating rules for any attributes that uniquely identify an object in the connected system.

WORKAROUND

Do not configure the attribute updating rules for the said attributes.

54467

Quick Connect Sync Engine may return an error message when you attempt to synchronize group memberships on data systems connected through the Generic LDAP connector.

WORKAROUND

  1. Ensure that mapping rules are configured for all classes of objects that are members of the groups to be synchronized. To configure mapping rules, use the "Mapping" tab in the Quick Connect Administration Console.
  2. Ensure that Naming attributes are defined for all classes of objects that are members of the groups to be synchronized. To define Naming attributes, use the "Connection Information" tab in the "Connection Properties" dialog box for the connected system with which you experience the described issue.

56121

You may encounter the following error while running an updating step from some connected system to Oracle Database: "ORA-01031: insufficient privileges".

This problem occurs if the user account under which Quick Connect Sync Engine connects to Oracle Database does not have sufficient rights to grant the SYSDBA and SYSOPER privileges to the Oracle Database users that participate in the updating step.

WORKAROUND

Make sure the account specified in the connection settings for the target Oracle Database system has sufficient rights to grant the SYSDBA and SYSOPER privileges to Oracle Database users.

166915

When synchronizing passwords to Oracle Database connected through the Oracle User Accounts Connector, you may encounter the following issue: Authentication type may be unexpectedly changed for some Oracle Database users from global or external to database authentication.

WORKAROUND

For each affected user, manually change authentication type back to global or external. Note that Quick Connect only supports password synchronization for users that access Oracle Database through database authentication.

167287

Unexpected behavior when a custom SQL query specified in the Quick Connect Administration Console references an object attribute that does not participate in the synchronization operation: When running such a query, Quick Connect may fail to display any warning that the attribute cannot be found. This issue only affects SQL queries specified for Oracle Database connected through the Oracle User Accounts Connector.

WORKAROUND

Correct your custom SQL queries to exclude all attributes that do not participate in the synchronization operation.

167296

Your custom SQL query specified for Oracle Database connected through the Oracle User Accounts Connector may fail to work as expected. This issue only occurs if the SQL query contains names of Oracle Database users, roles, and/or privileges that include lower-case letters.

WORKAROUND

Correct the names of Oracle Database users, roles, and privileges in the SQL query so that they include upper-case letters only.

167303

Unexpected result of a provision operation when a custom SQL query specified in the "SQL queries to run after user provisioned" option fails to complete successfully: Quick Connect may not automatically map some or all objects created in the target Oracle Database system in the result of the provision operation. The expected behavior is that Quick Connect should properly map each provisioned object. This problem only occurs if Oracle Database is connected through the Oracle User Accounts Connector.

WORKAROUND

  1. Ensure that the SQL queries specified in the "SQL queries to run after user provisioned" option can complete without errors (if necessary, correct coding errors in the SQL queries).
  2. Manually map the objects that were created in the target Oracle Database system during the provision operation. Alternatively, you can delete these objects, and then rerun the provisioning step.

167392

A synchronization step configured to update the values of UniqueID attributes (the attributes you use to uniquely identify objects in the connected data system) may not update the values of some or all such attributes.

This issue only affects the data systems to which Quick Connect Sync Engine is connected via one of the following connectors: Microsoft SQL Server Connector, Oracle Database Connector, MySQL Connector, or IBM DB2 Connector.

WORKAROUND

Do not perform the update operation on the UniqueID attributes in any of the above-listed data systems.

211189

A synchronization step that uses an SQL query to select and modify data in the connected system may fail with an error message similar to the following: "Synchronization steps aborted. Details: Unknown column '<ColumnName>' in 'field list'." This issue only occurs when the database table column name in question contains spaces.

WORKAROUND

Make sure that there are no spaces in the names of the database table columns participating in the synchronization.

-OR-

Configure and use a single-word alias for each database table column whose name contain spaces.

211746

System requirements

Before installing and using One Identity Quick Connect for Base Systems 2.4.0, ensure that your system meets the following minimum hardware and software requirements.

Quick Connect for Base Sysytems requirements

One Identity Quick Connect for Base Systems requirements

 

Table 3: One Identity Quick Connect for Base Systems requirements 

Requirement

Details

Processor

1 GHz or faster, x86 and x64 architecture is supported.

Memory

512 MB of RAM; 1 GB or more recommended.

Hard disk space

250 MB or more of free disk space. The amount of required hard disk space depends on the number of objects being synchronized.

Operating system

Your computer must run one of the following operating systems with or without any Service Pack (32- or 64-bit edition):

  • Microsoft Windows Server 2016

  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2008 R2, Standard or Enterprise
  • Microsoft Windows Server 2008, Standard or Enterprise
  • Microsoft Windows Server 2003 R2
  • Microsoft Windows Server 2003

One Identity Quick Connect Sync Engine

One Identity Quick Connect Sync Engine version 5.5

Oracle Database

The computer running One Identity Quick Connect Sync Engine must have the following software installed:

  • Oracle Client 11.1, 11.2, or 12c
  • Oracle Net Services
  • Oracle Data Provider for .NET 2.0 11.1.0.7.20

IBM DB2

The computer running One Identity Quick Connect Sync Engine must have the following software installed:

  • IBM Data Server Client supplied with the IBM DB2 version you want to use as a connected data system.

ODBC-compliant data source

The computer running One Identity Quick Connect Sync Engine must have the following software installed:

  • An ODBC driver providing access to the ODBC-compliant data source you want to use as a connected data system.

MySQL database

The computer running One Identity Quick Connect Sync Engine must have the following software installed:

  • Connector/Net 6.5 (an ADO.Net driver for MySQL)

Supported data systems

Below are the data systems supported by the connectors included in the One Identity Quick Connect for Base Systems package.

 

Table 4: Supported data systems

Connector

Supported data systems

Delimited Text File Connector

 

Generic LDAP Connector

  • Active Directory (AD DS and AD LDS formerly known as ADAM)
  • Directory service based on OpenLDAP 2.2 or 2.4
  • Sun One Directory Server version 5.2.

NOTE:Generic LDAP Connector may also work with other implementations of LDAP not listed here. However, Quest Support only supports the above-listed implementations. You may try working with other implementations of LDAP at your own risk..

Novell eDirectory Connector

Novell eDirectory 8.x

OLE DB Connector

Any data source accessible via an OLE DB provider.

Oracle Database Connector

Oracle9i Database, Oracle Database 10g, Oracle Database 11g, and Oracle Database 12c

Oracle User Accounts Connector

Oracle9i Database, Oracle Database 10g, Oracle Database 11g, and Oracle Database 12c

Microsoft SQL Server Connector

Microsoft SQL Server 2000, 2005, 2005 R2, 2008, 2008 R2, 2012, 2014, and 2016

Sun One Directory Server Connector

Sun One Directory Server 4.12, 4.13, 5.0, 5.1, and 5.2

MySQL Connector

MySQL database hosted on MySQL Community Server 5.0, 5.1, 5.5, and 5.6

OpenDS Connector

Directory service based on OpenDS 2.3

Red Hat Directory Server Connector

Red Hat Directory Server 8.2 and 9.0

IBM DB2 Connector

  • IBM DB2 Express-C 9.7 and 10.1
  • IBM DB2 for Linux, UNIX and Windows 9.1, 9.5, 9.7, 9.8, and 10.1
  • IBM DB2 for z/OS 8, 9, and 10
  • IBM DB2 for i 5 (release 4), 6 (release 1), and 7 (release 1)
  • IBM DB2 Universal Database (UDB) for Windows, UNIX and Linux 8
  • IBM Informix 11.10

OpenLDAP Connector

Directory service based on OpenLDAP 2.2 and 2.4

ODBC Connector

Any data source accessible via an ODBC driver.

Related Documents