Quick Connect for Base Systems 2.4 - Release Notes

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Processor

Memory

Hard disk space

Operating system

One Identity Quick Connect Sync Engine

Oracle Database

IBM DB2

ODBC-compliant data source

Delimited Text File Connector

Generic LDAP Connector

Novell eDirectory Connector

OLE DB Connector

Oracle Database Connector

Oracle User Accounts Connector

Microsoft SQL Server Connector

Sun One Directory Server Connector

MySQL Connector

OpenDS Connector

Red Hat Directory Server Connector

IBM DB2 Connector

OpenLDAP Connector