Skip to main content

18 November 2026

· 5 min read

badge

To receive updates about new posts and release notes, subscribe to our RSS feed: https://documentation.omadaidentity.com/horizons-release-notes/rss.xml

Changes ​

New authentication types for SAP SuccessFactors​

The SAP SuccessFactors now support additional authentication types that align with the authentication methods:

  • OAuth2 Client Credentials - authentication through SAP Identity Authentication Service (IAS) with OpenID Connect (OIDC). For more information, see OAuth2 Client Credentials.
  • OAuth2 SAML without an external identity provider - the SAML IDP Endpoint field is now optional. If you leave it empty, Omada Identity generates and signs the SAML assertion locally. Using an external identity provider is still supported, and existing OAuth2 SAML configurations continue to work without changes. For more information, see OAuth2 SAML.

The Basic authentication type remains available. You select the authentication type in the Authentication type list of the collector and in the Authentication mode parameter of the connector. For more information, see Data import and Data provisioning.

deprecation

In May 2027, the SAP SuccessFactors endpoint that generates SAML assertions is scheduled to be deprecated. To avoid depending on it, leave SAML IDP Endpoint empty.

Resolved bugs and issues ​

Unnecessary provisioning jobs created for already assigned resources​

We have fixed an issue where RoPE created provisioning jobs for resource assignments that already existed in the target system, for example, AD group memberships. For large calculation batches, RoPE reads the actual resource assignment data in several parts. A defect in how these parts were retrieved caused some existing assignments to be left out. The calculation treated the omitted assignments as missing and created provisioning jobs to assign them again. In larger volumes, these jobs could exceed the provisioning threshold and put the provisioning queue on hold. The next calculation read the data correctly, so the status returned to OK.

The stored assignment data was always correct, and no access was removed. The issue occurred only for large calculation batches, which is why it appeared intermittently.

The retrieval of resource assignments in multiple parts has been corrected, so RoPE now works with the complete actual state.

INC-318652

Cleanup import profile timing out during initialization​

We have fixed an issue where the cleanup import profile failed repeatedly with a timeout during the initialization of the cleanup in RoPE Calculator, for example, with the Execution Timeout Expired error. The issue had two causes. First, the initialization used extensive locking and waited for locks held by other operations, which caused it to exceed the timeout even though the volume of data was small. Second, when there was a large backlog of data to be marked for cleanup, the cleanup component marked the rows in chunks without reporting any progress, so the import timed out even though the cleanup was working correctly. The next cleanup import found the rows already marked and completed the deletion.

To resolve the issue, the following changes have been made:

  • The number of re-submitted messages has been reduced, which lowers the risk of blocking.
  • An option of less extensive locking is now available for cases where the first change is not sufficient.
  • During initialization, the cleanup component now reports progress after each chunk that does not complete the initialization, which prevents the cleanup import from timing out while the initialization is still running.

INC-320371, INC-318607

Identities not processed when Service Bus message expires during long import​

We have fixed an issue where identities were left unprocessed after a long-running import, for example, an import that received a full data set from the source system after a change of mappings. When a message with identities waited in the queue or was processed for a long time, its Azure Service Bus lock expired, and the message was lost (MessageLockLost). As a result, the identities contained in that message were not processed, and the import ended with an error in the processing step.

The Identity Merge component now renews the lock of the message while it is being processed, so the message no longer expires during large imports.

INC-320738

Imports failing with a timeout during peaks in import activity​

We have fixed an issue where there was a risk of imports failing with a timeout error when an unusually high number of imports ran at the same time. The service that coordinates imports took on more work than it could process, ran out of resources, and restarted several times. Imports running in that period failed with a timeout error.

The service now limits how much work it takes on at once, so peaks in import activity no longer overload it.

INC-321269

Initial password displayed in clear text in task details​

We have fixed an issue where the value of an attribute configured as a secure string, for example, the initial password in the Entra ID connector, was displayed in clear text in the task details of a create operation.

Values of attributes configured as secure strings are no longer displayed in clear text in the task details.

INC-320580