|
Memberships that have been added to One Identity Manager but not yet provisioned are marked as pending by a synchronization running at the same time. |
33144 |
|
When using the Database Transporter to import a synchronization project, the Do not change the start up configuration settings import option is not taken into account if it is enabled. Changes to the start configuration and to variables are overwritten in the target database. |
33153 |
|
If a membership is added to the One Identity Manager that has been previously deleted during target system synchronization, the change is not provisioned in the target system. |
33201 |
|
Under certain circumstances, when provisioning object properties, memberships of the affected objects in the target system are completely replaced with the memberships that exist in One Identity Manager, even though single provisioning of memberships is configured. This leads to changes made directly in the target system being overwritten.
The error occurs when schema properties dependent on an M:N property are to be provisioned. Due to the dependency, the memberships are also provisioned. If there is no membership operation in the DPRMembershipAction table at this time, the complete membership list is transferred. |
33205 |
|
If script variables are used in a variable set, the values of the default variable set are written to the synchronization log for the script variables instead of the values of the used variable set. During synchronization, the correct variable values are used.
Only the logging of the script variables is incorrect. Only logging of the script variables is incorrect. |
33229 |
|
Under the following conditions, the transport package for a synchronization project cannot be imported:
This causes an FK violation.
When transporting synchronization projects, the table relations' Ignore in superset handling property is not taken into account. The Database Transporter tries to delete referenced objects that exist in the target database but are missing in the transport package. |
33257 |
|
Error provisioning new memberships that have been deleted again in the One Identity Manager database (XOrigin='0') before the provisioning process for the new additions has been completed. |
33267 |
|
If single provisioning of memberships is configured for different custom target system types, several entries in the DPRMemberShipAction table are generated each time a membership is changed. One entry is created per target system type for which merge mode is set in the UNSAccountBInUNSGroupB table. However, only one entry is expected for the target system type containing the modified membership. |
33365 |
|
In the Synchronization Editor, if maintenance of synchronization buffers is started manually, an error message appears, which says that the DPR_MaintainDataStore process cannot be generated. |
33391 |
|
Error opening a synchronization project in the Synchronization Editor with a user that only has read permissions: Write permission denied for values: EditedBy, EditedSince.
When the Synchronization Editor opens a synchronization project, it writes the current user and time to the project and saves it in the One Identity Manager database (DRPShell table). This function prevents loss of data by informing other users, who try to open the same synchronization project, that it is already in use. However, the Synchronization Editor does not check if the current user has write permissions for this table. |
33394 |
|
In the synchronization log, an object is logged as modified. However, no change is logged for an object property although the synchronization log is configured such that modified properties and values are logged.
If the modified object property contains a secret value or the NULL, this change is not written to the synchronization log.
Solution: Logging has been altered. Secret values are logged as <hidden> and NULL values are logged as <null>. |
33402 |
|
Property mapping rules with a restricted direction of mapping and the addition Ignore mapping direction restraint on insert, do not work if synchronizing in the direction of the target system. |
33437 |
|
Certain Objects cannot be loaded during synchronization with a native database system. The following error message appears: No suitable key property found for reloading!
The value of the key property corresponds to the default value of the respective data type. For example, if the primary key has the Integer data type and a value of 0, the native database connector interprets it as empty and does not use the value to select the object. |
33258 |
|
SQL error synchronizing with the native database connector if, in the connection configuration to the external database, a pattern-based strategy for running data operations is defined and a referenced column name contains a space character.
Solution: The database connector uses the ScriptSafeIdentifier. Column names with special characters are now referenced if the special character is replaced by an underscore. Special characters are everything apart from letters, numbers and underscore.
Example: Insert Into MyTab([ColPK],[Col Spaces]) Values(%ColPK%, %Col_Spaces%) |
33274 |
|
New objects cannot be loaded during synchronization with a native database system. This error message appears: Unable to create the primary key where clause for system object ... |
33370 |
|
Error setting up a synchronization project for a CData ADO.NET Provider database with the native database connector. The error only occurs if the driver version 2020 is used. |
33484 |
|
The synchronization templates for Oracle E-Business Suite and SCIM add the reference scope with a German display name.
Patches with patch IDs VPR#33259_SCIM and VPR#33259_EBS are available for synchronization projects. |
33259 |
|
Error writing objects with the SCIM connector if the target system does not support queries with the Expect: 100-continue HTTP header option. The query is answered with HTTP status 417 Exception failed. The SCIM connector identifies this as an error and ends the process. |
33220 |
|
If a complex schema property is defined in the SCIM connector schema, its child schema properties might not be return by the SCIM connector. Thus the schema property are missing in the Synchronization Editor. For example, in the target system's schema view in the MappingEditor. |
33233 |
|
If a complex schema property is marked as a mandatory property in the SCIM schema, provisioning fails because a mandatory property is not mapped. |
33241 |
|
Error synchronizing with the SCIM connector if the id schema property of an object is a compulsory field.
In One Identity Manager, the id schema property is labeled as read-only in adherence with the SCIM specification. If the custom schema extension of the id schema property is added to an object as writeable, the property is still mapped as read-onlyin the One Identity Manager's extended schema. Therefore, in the object's PUT request, the id is not transferred. The SCIM provider responds with the error Missing required attribute [id]. |
33336 |
|
Error provisioning memberships if the SCIM provider supports the PATCH method.
An error occurs in SCIM when writing the members~vrtIDandType virtual schema property, which should distribute individual values to the members~type and members~value child schema properties. |
33459 |
|
The SCIM connector does not properly state that a SCIM provider does not supports filters. System filters can be defined in the synchronization project. However, this is not effective if the SCIM connector accesses the target system. |
33483 |
|
In One Identity Manager you can create Active Directory objects that differ only in diacritical characters (for example ê, ü). This is not permitted in Active Directory. A process step with the status Frozen is created because this object already exists in the Active Directory. |
33032 |
|
The home and profile directory of an Active Directory user account are deleted immediately once the user account is marked for deletion. |
33202, 33092 |
|
In Manager, if you open the master data form for several Active Directory groups selected by multi-select and open the Account manager drop-down menu on the form, then the program no longer reacts. |
33177 |
|
If an Active Directory schema in an existing synchronization project is updated after it was created by a project template, all the schema types that were not already saved in the schema are missing the contents from the calculated schema properties AuxiliaryClasses, ContainerClasses, AllSuperClasses, and AllSearchClasses. |
33246 |
|
Assigning an Active Directory computer to a device does not queue a ADS-K-ADSMachineInADSGroup recalculation task. This means that groups inherited through the device are not assigned to the computer. |
33420 |
|
On the master data form for Active Directory user accounts, the control for the Dial-up permitted property is always enabled, even if the user only has read-only access to the property. The value can be changed and saving does not cause an error. However, the changes are not saved. |
33463 |
|
The type testing for loading Active Directory object is too strict. |
33138 |
|
Error assigning an employee to an Active Directory user account if the user account has a linked Microsoft Exchange mailbox without being linked to a user account (EX0Mailbox.UID_ADSAccountLinkedMaster). |
33317 |
|
The contact data of an Azure Active Directory user account with an Exchange Online mailbox can only be maintained if the mailbox is of recipient type User Mailbox (UserMailbox). |
33191 |
|
Error synchronizing Azure Active Directory groups that are assigned to Azure Active Directory administrator roles.
To correct this issue, a member filter that only includes user accounts has been defined in the DirectoryRole mapping. A patch with the patch ID VPR#33399 is available for synchronization projects. |
33399 |
|
Exchange Online synchronization fails when updating telephone numbers of Exchange Online mail users linked to an Azure Active Directory user account of type Guest.
A patch with the patch ID VPR#33476 is available for synchronization projects. |
33476 |
|
The columns O3EDynDL.Notes, O3EMailContact.Notes, O3EMailUser.Notes, and O3EUnifiedGroup.Notes are too short. |
33392 |
|
Error message insufficient when parsing the distinguished name (DistinguishedName) of an LDAP object. The failed object does not appear in the message. |
33310 |
|
Error loading SAP user accounts if SAP client salutations are defined that are identical in more than one language. The salutation references cannot be resolved.
A patch with the patch ID VPR#33147 is available for synchronization projects. |
33147, 33447 |
|
In the Synchronization Editor, if you open the target system browser for a connected SAP R/3 environment and select a single object in any result list, no object properties are displayed. |
33168 |
|
When extending the SAP schema with a schema extension file, no error is detected if the OutStructure attribute in a function definition has the correct data type BAPIRET2, but the name of the SAP structure is not RETURN, RETURN0 or BAPIRET2. |
33200 |
|
If different tables are used in the schema type definition of a schema extension file for calling the object list or calling single objects, SAP R/3 only accesses the tables with the ListObjectsDefinition attribute when setting up the schema and loading objects. |
33218 |
|
SAP roles are labeled as deleted or outstanding by synchronization if the same role is inherited both as single role and through a collective role as well. This happens when the TargetSystem | SAPR3 | KeepRedundantProfiles is set. |
33244 |
|
The overview form for an SAP role does not show which IT Shop shelves the role is assigned to. |
33361 |
|
During synchronization with an SAP R/3 environment, the error messages in the synchronization log multiply if Continue on error is set in the synchronization project. |
33416 |
|
If a change to the salutation in an SAP user account is provisioned, the Check Properties SAP check fails. This happens if the SAP R/3 connector accesses the target system during provisioning using a login language other than the original language of the salutation.
A patch with the patch ID VPR#33423 is available for synchronization projects. |
33423 |
|
If an employee's central password is changed in One Identity Manager, this employee's SAP user account is locked. |
33450 |
|
If a connection to IBM Notes cannot be established immediately because another process is already using the system, the connection waits for the process to end and a warning is issued if it cannot connect while waiting. To issue the warning, access is required to a property of a Domino Server that cannot be reached. The follow error occurs: "Domino server not connected." |
33283 |
|
If the TargetSystem | NDO | MailBoxAnonymPre configuration parameter is not set, Notes user accounts are not anonymous when they are locked. If these user accounts are later unlocked, the NDO_NDOUserInGroup_ChangeNamesOn(un)Lock process is run although the full names of the user accounts have not been changed. |
33330 |
