Skip to main content

Version 1.17.4

Release Date: July 25, 2026 Release Type: Release Candidate

This was a Release Candidate published to the staging channel; its content was validated and is included in 1.18.0, the first release on the single product version line. This release completes the 1.17 line — REST multipart handling, OFTP2 delivery-error visibility, OpenShift / rootless deployment and service-user traceability in logs, along with import, configuration and designer improvements — plus all bug fixes of the 1.17 release-candidate line.

Backend Server​

New Features​

  • REST multipart / form-data handling: The inbound REST listener now correctly preserves and forwards multipart/form-data request bodies, and can optionally record each part in the attachment log, with a configurable size cap to protect memory against very large uploads.
  • OpenShift deployment support: Official OpenShift-native deployment manifests (restricted security context, an operator-managed PostgreSQL, native Routes) plus additional rootless container image variants, alongside the existing Kubernetes/Azure option.
  • OFTP2 delivery-error visibility: OFTP2 transfer problems (a duplicate-file rejection, or a partner disconnecting without a delivery receipt) now surface in Message Monitoring as clear errors, and virtual-file identifiers are made unique to avoid false duplicate-file rejections on resend.
  • Service-user name in authenticated logs: For Basic- and JWT-authenticated inbound requests, message logs record the authenticating service user's name, giving clearer traceability of who sent a message.

Bug Fixes​

  • Binary request bodies (for example an image or PDF uploaded as a multipart part) now log correctly; previously embedded null bytes broke log persistence and the corresponding attachments appeared missing in monitoring.
  • The Set Context node now produces valid JSON when a mapped value is null or an empty array/object, instead of malformed output that broke downstream processing.
  • Attachment logging (when Elasticsearch is disabled) now uses parameterized database writes, closing a SQL-injection exposure, and stamps proper timestamps so retention and time-window filtering work.
  • XI receiver faults now carry the real error category, code and detail into the flow error and monitoring, so operators can distinguish an interface mismatch from a missing receiver.
  • Basic-authentication credential lookup for the XI connector now resolves correctly instead of always returning empty.
  • A flow's per-flow global-configuration override now only blocks an inherited setting; it can no longer force-enable a setting or replace a global's value.
  • The Service Methods (XSD/WSDL) generator now includes operation descriptions and honors a configured target namespace.
  • On Kubernetes, the bundled Kafka broker now retains its topics, consumer offsets and metadata across pod restarts.

Frontend Server​

New Features​

  • EDI converter connector and EDI schema management: A unified connector for converting EDI messages, plus management of the EDI schemas your flows rely on.
  • Guided import with conflict analysis: Import a package or flow-mapping archive with an up-front analysis of exactly which flows, resources and mappings already exist, then choose overwrite or skip per item or in bulk before applying. It runs in the background with progress and cancellation, gives clear messages for empty or invalid archives, and leaves the existing one-click import unchanged.
  • Global flow configuration with per-flow overrides: Define reusable configuration values once and apply them across flows, or override/block them for individual flows. A flow's values now travel with it on export and import, and deletion is guarded by a where-used check.
  • Detailed flow change history: Each flow update records exactly what changed — which steps were added, removed or modified and which fields changed — filtered to the fields actually visible in the designer.
  • Message log identity tracking and export: Message logs capture who triggered each message and which credential and identity were used, and these fields are included in the CSV export.
  • REST multipart/form-data support: The REST start connector can optionally accept inbound multipart/form-data uploads, log the attachments, and forward the body.
  • OAuth2 signed-JWT client authentication and login improvements: When MIP requests OAuth2 tokens, it can authenticate with a signed JWT (client_secret_jwt or private_key_jwt) instead of a shared secret, selectable per credential. OAuth2 login redirects resolve the correct public address, the interface knows when OAuth2 login is available, and an unreachable gateway is handled gracefully.
  • Connector refinements: X.400 connector settings were refined around O/R addressing, TLS, delivery reports and body-part type (existing flows continue to load); FTP and SFTP connections accept additional custom parameters; and OFTP2 connections show which flows use them on both sending and receiving sides, blocking deletion while in use.
  • OpenShift support and health probes: Native OpenShift deployment manifests and rootless container images, plus liveness and readiness probes that fail fast when the database is unreachable, for reliable rolling deployments.

Bug Fixes​

  • Version-history activity entries are stamped with their own save time instead of the previous save's time.
  • The credential Confirm Sync action now creates the API management consumer when one does not yet exist, so the credential reaches the gateway and appears in the Consumer list.
  • Deleting a service user cleans up its related OAuth2 and API-management bindings, avoiding orphaned records.
  • Certificate Where Used now includes Kafka connectors, so certificates in use by Kafka flows are listed and protected from deletion.
  • The AI-monitoring certificate table lists only certificates within the expiry threshold or already expired, matching its banner.
  • Importing a flow whose name collides with an existing flow no longer fails — it is renamed automatically.
  • API management route provisioning retries while the gateway settles, and MIP no longer connects to the gateway at all when API management is turned off.

Frontend Web​

New Features​

  • Resource pickers and safeguards in editors: Cascading Flow-to-Resource pickers to insert XSLT, XSD and flow scripts, a client-side XSD sample-XML generator, and save controls that warn when you edit resources used by live flows.
  • EDI converter and schema management: A unified EDI converter connector node plus an EDI Schemas management page.
  • OFTP2 connection usage modal: OFTP2 connections show a where-used modal listing the dependent flows and certificates/keystores before you change or delete them.
  • Flow designer productivity: Multi-node selection with Ctrl+click and group copy/paste, a multi-line SQL editor for JDBC query fields, and clearer Multicast guidance that warns (but no longer blocks) when a non-Direct connector follows a Multicast.
  • Richer activity history: The Activity panel shows human-readable node and field change details for flow updates, hiding empty fields and grouping cleared values.
  • A new REST Multipart Attachment Logging toggle.
  • OpenShift support: Ready-to-use OpenShift manifests and multi-variant container images.

Bug Fixes​

  • The Consumer list in API management no longer shows "Nothing Found" over a populated list.
  • The XSD/WSDL schema designer generates correct schemas — fresh previews, SOAP 1.1 and 1.2 output, full input validation, and confirmation before destructive edits.
  • Per-flow overrides of global flow configuration are correctly block-only, with an accurate in-use warning on delete or disable.

Health Check​

New Features​

  • Component version details: The system-information view now shows real version numbers for MIP components — backend server, web server and running container images — in containerized deployments where these previously showed placeholder values.
  • OpenShift deployment support: MIP Health Check can be deployed on OpenShift/ARO using native manifests and rootless image variants, with a ready-made monitoring and dashboard integration.
  • Fast-failing health probes: Dedicated readiness and liveness probes let an orchestrator detect an unhealthy or database-unreachable instance within seconds, and allow the service to start even while the database is temporarily down instead of getting stuck in a restart loop.

Bug Fixes​

  • System memory usage is reported accurately; it previously counted reclaimable buffer/cache as used and could read as high as ~96% on a largely idle machine.
  • Time-window filtering of health data honors an explicit timezone offset and a configurable business time zone, so charts line up with the intended local day.

This is a Release Candidate (pre-release); its validated content ships in 1.18.0. Previous: 1.17.3