The October 2026 release includes the following important notices and upcoming changes.
Preview lifted
Effective in the October 2026 release, the following functionalities are generally available and production-ready. Previously, these functionalities were only available in preview.
Auto-tuning for database ingestion and replication tasks
You can enable auto-tuning on database ingestion and replication initial load tasks and the initial load phase of combined load tasks. Auto-tuning automatically sets optimal values for pipeline parameters, including source partition count, helper thread counts, distributor counts, and the number of rows per output file. To enable auto-tuning for a task, select the Auto-Tune option on the last page of the task configuration wizard.
Log-based CDC for encrypted SAP HANA redo and archive logs
Database ingestion and replication jobs that use Log-based CDC can now capture changes from encrypted SAP HANA online redo logs and archive logs. When you configure the SAP HANA Database Ingestion connection, provide the Key Backup Password and Key Backup Data Path to allow the connector to decrypt AES-256 CBC encrypted online redo and archive log files. The connector checks each log file to detect whether encryption is active. This action ensures jobs continue uninterrupted even if you turn encryption on or off on the source database while a job is running.
Apache NiFi 2.5.0 runtime engine for Streaming Ingestion and Replication
Streaming Ingestion and Replication uses the Apache NiFi version 2.5.0 runtime engine. No user action is required. The upgrade includes key updates to custom processors and AMQP NAR components.
Reinstated support
Effective in the October 2026 release, historical statistics for job monitoring in Streaming Ingestion and Replication is reinstated and is available.
You can view the historical performance statistics for jobs on the Performance tab in My Jobs and Operational Insights. The performance charts track data movement trends, such as the total number of messages and the data volume transferred between the source and the target. You can use the charts to compare a job's current performance against its history, spot unusual changes, and troubleshoot issues.
Deprecated support
Effective in the October 2026 release, OAuth 2.0 Username-Password Flow authentication in Salesforce Mass Ingestion Connector is deprecated because Salesforce is retiring the SOAP API login() call in API versions 31.0 through 64.0 to align with enhanced cybersecurity standards. For more information, see Platform SOAP API login() Retirement.
Deprecated functionality is supported, but Informatica intends to drop support in a future release. Informatica requests that you transition to different functionality before the functionality is dropped.
Informatica intends to drop support for OAuth 2.0 Username-Password Flow on May 1, 2027. In the interim, transition to OAuth 2.0 JWT Bearer Flow authentication.
Additionally, you can no longer create new connected apps in Salesforce. Existing connected apps continue to work, but you cannot create new ones. To create a new Salesforce Mass Ingestion connection, configure an External Client App in Salesforce. For more information, see Create an External Client App. To migrate an existing connected app for your Salesforce Mass Ingestion connection to an external client app, see Connected App to External Client App Migration.