📄️ Active Directory task error when updating object
The Active Directory (AD) connector reported errors for modify provisioning tasks for users sharing the name with a computer object in AD. The issue has now been resolved and errors no longer occur.
📄️ Password visible in the connection string
The password hasn't been hidden in the connection string for SQL connector. Now the password is replaced by asterisks * and is no longer visible.
📄️ Exchange extension attributes migration failure
The extension attributes migration for the exchange system was failing. The issue has now been resolved and the migration processes is successful.
📄️ Connectivity package export issue
There was an issue with creating connectivity package to be exported. In the dialog box allowing the user to override export parameter values, an integer type parameter had a non-empty value and the connectivity package was not created. The issue has been resolved.
📄️ Scope is omitted while provisioning an account
The validation for user objects was not included if dn in the provisioning task was defined in the scope in the connector settings resulting in the scope being omitted during provisioning. The validation has been added and the provisioning process runs correctly.
📄️ Export errors not visible in the Identity Governance and Administration system
The export errors in onboarded system were not visible in the built-in Omada Identity system. The issue has been resolved and you can monitor errors in onboarded systems via Identity Governance and Administration system.
📄️ Exchange migration fails
An issue with the migration of the extension attributes during the Exchange migration process has been resolved and is now successful.
📄️ Potential memory leak
For the REST connector failed jobs with multiple tasks consumed extensive amounts of memory resulting in OutOfMemory issues. The issue is resolved by the addition of the errorResponseFilter parameter. Enabling it overrides the default behavior during error occurrance, when the whole response is logged. Instead, it provides JsonPaths to properties which should be extracted from the response body.
📄️ Archive view logic fails for NULL values
There was an issue with the custom view failing on null values. The issue has been resolved and if it can't be determined if an attribute is single or multivalued it is registered as a multivalued one, not returning null.
📄️ Data model JSON converter
There was an issue with the appropriate conversion of JSON payload into data model. The issue has now been fixed and the properties are specified as multivalued, by the converter, if the JSON payload contains array tokens.
📄️ TLS version selection for SAP connector
Choosing the transport layer security (TLS) protocol for the SAP connector was unavailable. It has been resolved and the TLS version can be configured in the web services task.
📄️ Issue with migrating collectors
There was an issue with migrating two Active Directory systems trusting each other. The issue has been resolved and the migration process is successful.
📄️ Unexpected error during database access
There was an issue where all provisioning-related failures were logged with the generic error message.
📄️ ServiceNow ITSM - existing sc request item not found
There was an issue with the ServiceNow relay connector that resulted in creating request item duplicates. The issue has been resolved and the duplicates are no longer created.