--- title: "LDP Release 26.3.3" slug: "ldp-release-26-3-3" updated: 2026-09-16T07:34:11Z published: 2026-09-16T07:34:11Z canonical: "docs.lobstersoftware.com/ldp-release-26-3-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.lobstersoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # LDP Release 26.3.3 ## Release notes - Lobster Data Platform 26.3.3 Release date: 2026-08-26 > [!TIP] > ### Known issues > > **Resolved with** [**26.3.6**](/v1/docs/ldp-release-26-3-6): The configuration for sending emails may not be transferred correctly to **Base settings** **>** **System Emails**. For the workaround, see [System email configuration not migrated (26.3.3 and later)](/v1/docs/en/known-issues-26-3-4-26-3-5). ### New Features & Improvements #### LDP-7879 The Lobster Data Platform can now use a faster driver for connecting to Lobster Bridge. ### Bug fixes #### LDP-8524 Sessions now hand off correctly between cluster nodes. Previously, in high-availability setups with CSRF protection enabled, a login served by a non-owning node could fail with an internal error. #### LDP-8504 System benchmark: Storage folders on the same network share are now grouped as one device, even when reached via symlinks or multiple mounts, instead of being listed separately. #### LDP-8484 Pathfinder chat overlays now display timestamps and dates correctly. #### LDP-8477 Lobster Bridge: Inbound and outbound folders with umlauts can now be created for AS2 settings. #### LDP-8472 - Email settings are now applied in the application in all cases. - Customer-defined email channels are validated to confirm they exist before use. - The internal channel is now reliably retrieved from the database. #### LDP-8464 Pathfinder's MAPS agent now correctly updates integration profiles that contain numeric fields such as `interval` and `certId`. #### LDP-8411 DMZ: A custom `wait.time` set in the DMZ's `etc/forward.properties` is now applied immediately after a DMZ start or restart, and consistently across all forward destinations. #### LDP-8405 OpenAPI: The Swagger UI can now be opened from Phase 1 without an “Access Denied” error. The server used for access must be listed in `hub.datawizard.api.viewer.whitelist`, including its port. For example: `platform-test.lobster.de:443`. #### LDP-8356 IoT Client Configuration: The Certificate Search Term, Application URI, and Application Name are now persisted to the `iotclient.xml` configuration file. #### LDP-8348 Transport Manager: The Blob Type of Cloud Storage response paths no longer changes from “Block” to “Append” after transport. #### LDP-8344 Inactive items in the profile overview are now shown in the correct color. #### LDP-8342 System emails now support multiple recipient email addresses separated by semicolons. #### LDP-8302 API Manager: User access permissions are now enforced for MCP endpoints. Only authorized users can access and invoke restricted tools and endpoints as configured. #### LDP-8277 The Email connection type drop-down now saves the selection correctly when switching to the SMTP option. #### LDP-8268 Salesforce Integration: `SalesForceBulkIUV2` no longer fails with “No connection found for alias” when the target structure contains multiple nodes. #### LDP-8188 Reports: PDF reports can be generated for a selected profile again; the internal template files are found reliably. #### LDP-8022 Drag-and-drop mapping and tree navigation now work when strict web security rules are enforced, so profile structures behave as expected across all security configurations. #### LDP-7985 PDF Processing: Aspose PDF classes no longer consume excessive heap memory — close to 6 GB in some cases — when loading fonts in message consumer threads. #### LDP-5901 User Settings: Removed the obsolete option “Double click opens module entries in a new browser tab,” which no longer had any function. Software component that is installed on a customer's system and communicates with the Lobster Data Platform via an encrypted tunnel. The bridge allows the platform to access local databases as well as execute ETL/ELT jobs and AS2 transfers on-site. Lobster Data Platform's AI helper that answers questions based on product documentation and can generate content such as cron expressions, SQL queries, and regular expressions (regex). The range of functions is continuously expanded. Communication protocol for secure EDI data exchange via HTTP/HTTPS. AS2 encrypts and signs messages and confirms receipt via MDN. AS2 is defined in the RFC 4130 standard. **MAPS** stands for **M**apping **A**I **P**athfinder **S**uggestions. It's an AI-assisted mapping feature in the DataWizard profile editor that analyzes source and destination field structures of a profile and calls the Lobster Pathfinder AI agent to suggest how source fields should be mapped to destination fields. An optional security layer between the internet and the Integration Server. The DMZ receives incoming traffic, forwards it in a controlled manner, and protects the internal system from direct external access. When the Integration Server restarts, it buffers incoming requests. Input: An input agent receives the data. It can work either as event based (e.g. FTP upload) or scheduled (cron). A module for the structured transfer of configuration objects between systems, such as from a development environment to a production environment. The Transport Manager packages profiles, partners, ETL/ELT pipelines, and other entries into transportable packages. **MCP (Model Context Protocol)** is an open standard published by Anthropic at the end of 2024 that enables AI systems to connect to external tools and data sources in a standardized, secure manner. MCP works like a USB port for AI: Instead of rebuilding each connection individually, it ensures a uniform connection option. Similar to how LDP integrates heterogeneous systems via standardized interfaces, MCP consistently connects AI applications with APIs and live data, including access control and data protection.