An error occurs when connectors that use the local SQLite cache to load an object list and the virtual schema properties from the synchronization configuration with a property type of Key resolution are used. The value is a schema property is not correctly determined and the synchronization unexpectedly quits with am error.
Error: The object <obj> does not have a value for key property <prop>. |
33532 |
Performance issues in the target system browser when reloading objects from tables with more than one primary key and no object key. |
33607 |
Incorrect logging of script variables in the synchronization log if a variable set other than the default one is used in the synchronization project. |
33627 |
When a synchronization project is imported with the DBTransporterCmd.exe program, the shadow copy is not deleted. This means that after importing the synchronization project is opened in its old state. |
33751 |
Error importing a synchronization project with the Database Transporter if the synchronization project already exists in the target database and several connected objects are deleted by the import. |
33835 |
If an empty value cannot be resolved for a schema property of Key resolution type, a warning is logged or synchronization stops, depending on the configuration. |
33877 |
Scripts for custom processing methods do not handle schema properties with values taken from the connected system. For example, if a custom processing method is run instead of the Insert method, the schema properties remain empty.
In custom processing method scripts, a third, optional parameter can now be given that passes the object value from the connected system. |
33979 |
The value in the XOrigin column cannot be changed by synchronization. |
33996 |
When publishing outstanding memberships in groups (UNSAccountBInUNSGroupB), the HandleOutstanding event is not triggered. |
34023 |
Error during synchronization when properties needed for resolving object references are missing from the objects in the synchronization buffer. |
34071 |
When native database columns are read or written with the native database connector, the date is converted to UTC. |
33661 |
The native database connector does not take the reference scope into account if it is defined as a system filter only. |
34257 |
Error connecting the SharePoint Online connector with the target system if legacy authentication with user name and password is disabled on the SharePoint server.
Error: [System.NotSupportedException] Cannot contact web site '<site>' or the web site does not support SharePoint Online credentials. The response status code is 'Unauthorized'.
TheSharePoint Online connector now supports authentication through an Azure Active Directory application with a self-signed certificate.
A patch with the patch ID VPR#33432 is available for synchronization projects. |
33432 |
Long runtimes for provisioning SharePoint Online user accounts, groups, roles, and permission levels. |
33582 |
SharePoint Online connector performance issues. Error: "... has not been initialized." |
33548 |
In the value list of the O3SRole.RoleTypeKind column, the values Reviewer, RestrictedReader, and RestrictedGuest are missing. |
34074 |
In certain circumstances, Unix user accounts with special characters in their passwords are not added correctly. Only a fraction arrives in the target system. Provisioning ends with the error:
[Sugi.Common.Exceptions.SugiParserException] Received unexpected EOF while parsing action results |
33592 |
When a new Unix user account is created, the parameter for the home directory is not taken into account. This means that the home directory is always created under /home/<user name>. |
33713 |
Error including a schema extension file in the SAP connector schema if the tables are defined after the functions in the file. |
33564 |
If a schema type is defined in a schema extension file that uses table definitions for the ListObjectsDefinition and ReadObjectDefinition attributes as well as function calls for the InsertObjectDefinition, WriteObjectDefinition, and DeleteObjectDefinition attributes, the parameters of the given function are missing in the resulting schema as schema properties of the schema type. |
33574 |
Error when user accounts inherit SAP roles (SAPUserInSAPRole) if the corresponding SAP user account client access (SAPUserMandant) is marked as outstanding.
Error 1: Although the TargetSystem | SAPR3 | AutoFillSAPUserMandant configuration parameter is not set or does not exist, valid assignments are generated.
Error 2: If the TargetSystem | SAPR3 | AutoFillSAPUserMandant configuration parameter is set, valid assignments are generated. But the client's assignment to the user account stays outstanding. This provisions the role assignment. The outstanding mark is not removed until the next time synchronization is run.
The SAP_ZUserInSAPProfile and SAP_ZUserInSAPRole procedures for calculating inheritance have been corrected. If the TargetSystem | SAPR3 | AutoFillSAPUserMandant configuration parameter is not set, the roles and profiles are not inherited by the user account and the entry in SAPUserMandant stays outstanding. If the TargetSystem | SAPR3 | AutoFillSAPUserMandant configuration parameter is set, the outstanding mark is removed and the roles and profiles are inherited by the user account
NOTE: SAP roles and profiles can then also be assigned directly if the assignment to the user account of the client that the roles and profiles belong to, is marked as outstanding. This removes the outstanding mark. |
33724 |
Passing parameter to functions that are defined in an SAP schema extension file is not always correct. |
33939 |
Very long runtimes for calculating memberships in SAP roles in One Identity Manager version 8.1.4. |
33959 |
The SAP synchronization project consistency check shows warning messages.
A patch with the patch ID VPR#33980 is available for synchronization projects. |
33980 |
When renaming SAP user accounts in the Manager, the Disabled password option is not taken into account. |
34059 |
The SAPUserInSAPHRP.Excluded column is not provisioned in SAP R/3 although it can be edited in the Manager.
A patch with the patch ID VPR#34081 is available for synchronization projects. |
34081 |
The description of SAP roles is divided into two fields in the SAP GUI. In One Identity Manager, the entire description is written in one column although there are also two fields available.
In the synchronization project, a new virtual schema property has been created to divide up the description. The map has been adapted. A patch has been provided to correct existing synchronization projects. |
34128 |
An SAP group can be assigned to SAP user accounts that are administered through a Central User Administration, in One Identity Manager only if the group's client is assigned to the user accounts. In the SAP R/3 environment, a user account can be assigned to the central client's group without the user account being authorized for the central client. |
34164 |
Error provisioning an SAP user account when the valid from date of the user account is greater than the valid until date. This data installation is now prevented in One Identity Manager. |
34245 |
Exchange Online dynamic distribution groups (O3EDynDL table) do not allow the empty included recipients (IncludedRecipients column) although it is not a mandatory field in the Exchange Admin Center. An error occurs during synchronization. The Customizer prevents the column from being empty. |
33730 |
Incorrect number of the Notes version in log messages when using IBM Domino Server version 10 or HCL Domino Server version 11. |
33654 |
Error provisioning Notes mail-in databases. |
33755 |
When a mail-in database is created, it is mandatory to enter the Notes domain that the mail-in database should belong to. There is a property mapping rule missing for transferring the value to the target system during provisioning of the mail-in database.
A patch with the patch ID VPR#33759 is available for synchronization projects. |
33759 |
The IBM Notes connector does not store the user ID file in the location specified in the TargetSystem | NDO | TempNetworkPath configuration parameter.
The configuration parameter has been deleted. Customized usage might require modification. Use the settings in the main data of the linked Notes domain or the allocated mail server. |
34302 |
When the system connection to an Oracle E-Business Suite is saved, parts of the connection credentials are saved twice.
A patch with the patch ID VPR#34008 is available for synchronization projects. |
34008 |
If an Active Directory global catalog is unreachable due to the firewall configuration, requests to the global catalog will not fail. Process steps that perform name resolution through a global catalog remain in the Processing state in this case.
Solution: A timeout of 65 seconds has been built into the Active Directory connector so that a request that is not answered within a certain time is considered to have failed. |
33807 |
When creating Active Directory user accounts, diacritical characters (for example, Å, Ø, or Æ) are not correctly taken into consideration in the templates and table scripts. The user accounts are not created. |
33590 |
The description of the TargetSystem | ADS | Accounts | NotRequirePassword configuration parameter does not match the behavior. The description has been adjusted. |
33500 |
Errors in the documentation of some Password Capture Agent properties in the One Identity Manager Password Capture Agent Administration Guide. |
33967 |
Errors may occur when synchronizing LDAP groups and their members if at least one member user account is not yet stored in the One Identity Manager database and is only found in the synchronization buffer. |
34211 |
Assigning an LDAP computer to a device does not queue a LDP-K-LDPMachineInLDAPGroup recalculation task. This means that groups inherited through the device are not assigned to the computer. |
33509 |
Error when provisioning memberships in LDAP groups. An attempt is made to write a empty value to the Member attribute of an LDAP group.
Error message:
Operation error message: A protocol error occurred.
Response result code: (2) ProtocolError
Response message: no values given |
33869 |
Issues if the Password property is a mandatory field in LDAP. For all schema classes that have this property, a vrtPassword is provided by the connector. The virtual property is mapped in the default. The actual Password property is not mapped. This leads to an error in the consistency check of the synchronization project as well as errors in provisioning. |
34091 |
The length of the LDAPAccount.RoomNumber column is too short. |
34099 |
An error occurs when checking an Active Directory password policy in the Designer:
VI.DB.DatabaseException: Database error 1: SQL logic error
no such table: ADSPolicyAppliesTo |
33770 |
The Custom and the User defined tabs on the main data form for cloud user accounts are both called Custom in the English user interface. |
33578 |
Error synchronizing a cloud application with the SCIM connector when using the ETAG property as a revision counter. |
33762 |
Not all changed objects are correctly viewed and updated when synchronizing a cloud application with revision filtering because the time zone of the SCIM provider is not taken into account. |
33949 |
Exception error during initial synchronization of a cloud application with the SCIM connector: Invalid token header. No credentials provided. |
33988 |
Authentication failure due to missing encoding when logging in to an Oracle cloud application using the SCIM connector. |
34123 |
The length of the AADUser.State column is too short. |
33954 |
Performance problems during synchronization if many-to-all tables are included in the mapping. |
34096 |
Simultaneous provisioning of multiple G Suite organizations fails (quota exceeded). |
33636 |
The Customizer prevents the primary email address of a G Suite user account from being changed if this involves using an email address that is already assigned as an alias. |
34160 |
The Customizer prevents the modification of Microsoft Exchange mailboxes when the Active Directory user account is disabled. |
34329 |
When exiting the System Connection Wizard for Microsoft Exchange, an error occurs if a password with two dollar signs ($) is entered in the connection parameters.
Error message: Unknown Variable (T)! |
34359 |
The Delete sensitive data process step does not always run reliably when the employee's central password is propagated to the user account. It might result in password fields in the database not being cleared.
The behavior has been changed as follows:
-
An employee's central password is now only passed on to user accounts belonging to target systems that are synchronized by the One Identity Manager (NamespaceManagedBy=VISYNC). In custom target systems, it must also be possible to perform write operations (IsNoWrite=0).
-
For read-only target systems (NamespaceManagedBy=ReadOnly), the employee's central password is no longer propagated to the employee's user accounts.
-
An additional process step has been implemented in the processes for user accounts. This waits until all user account's processes have completed. Then the user account's password data is deleted from the database.
The following processes were modified:
AAD_User_Insert
AAD_User_Update/(De)Activate
ADS_ADSAccount_Insert
ADS_ADSAccount_Update/(De-)activate
ADS_ADSAccount_Insert (ReadOnly)
LDP_Account_Insert
LDP_Account_Update/(De-)Activate
CSM_User_Insert
CSM_User_Provision
EBS_EBSUser_Insert
EBS_EBSUser_Update
GAP_User_Insert
GAP_User_Update/(De)Activate
PAG_User_Insert
PAG_User_Update/(De)Activate
SAP_SAPUser_Insert
SAP_SAPUser_Update
UNX_Account_Insert
UNX_Account_Update/(De)activate
NDO_NDOUser_Insert
NDO_NDOUser_Update
NDO_NDOUser_Insert (ReadOnly)
UCI_UCIUser_Insert
UCI_UCIUser_Update |
32671 |
Changing an employee's central password several times quickly results in an error.
Error: <Central Account> was changed by another user. |
34388 |