Skip to main content

Version 1.18.4

Release Date: August 20, 2026 Release Type: Stable

Deployed Integrations endpoint display restored, configurable platform encryption key, service-user and OAuth2 sync fixes, designer validation fixes, and Health Check reliability improvements.

Backend Server​

Bug Fixes​

  • Deployed Integrations show the same endpoint URLs as before the endpoint-catalog upgrade: Moving connector addresses onto the central endpoint catalog unintentionally changed the addresses displayed on the Deployed Integrations page for installations that configure a global HTTP endpoint variable. The displayed URLs now fall back to that legacy setting again and render byte-identical to previous releases; actual traffic routing was and remains unaffected.

Frontend Server​

New Features​

  • Configurable platform encryption key: Sensitive data encryption now uses the shared ENCRYPTION_KEY environment setting, unified across platform services, instead of a built-in key. Existing installations remain compatible: previously encrypted data still decrypts when no custom key is configured.

Bug Fixes​

  • Removing OAuth2 from an API now fully disables it on the gateway: In API Management, unsyncing OAuth2 from a published API now also removes the OIDC plugin from the gateway route. Previously the route could keep enforcing OAuth2 authentication even after protection was removed.
  • Deployed Integrations show the original endpoint addresses again: The Deployed Integrations page once again displays connector addresses based on the configured public endpoint (BACKEND_HTTP_ENDPOINT), exactly as before the endpoint catalog migration. Asynchronous callback URLs handed to remote systems are now always built from the functional base URL, so they never advertise an unreachable address.

Frontend Web​

New Features​

  • Safer service-user unsync with consumer cleanup: On the Service Users page, Unsync is now only enabled when an API-management binding actually exists, and after unsyncing you are prompted to optionally delete the corresponding API-management consumer. Sync status also refreshes immediately after a successful sync without reopening the dialog.

Bug Fixes​

  • OAuth2 service-user credential sync now works: Syncing an OAuth2 service-user credential to API management always failed with a validation error because the request carried the wrong field name. The sync now sends the expected field and completes successfully.
  • Re-uploaded WSDLs picked up in SOAP connector: After re-uploading a WSDL resource, the SOAP connector configuration now picks up the new bindings and operations immediately, without having to de-select and re-select the resource.
  • XSLT editor validation and scrolling: The XSLT editor now validates parameter and property names before saving, and the editor panels scroll correctly, including jumping to the line of a reported error.
  • XSD designer input validation and label fixes: The XSD designer validates element, schema, and WSDL method inputs to prevent invalid definitions from being saved, and the Copy/Duplicate actions now show correct labels.
  • JSON designer validation and OpenAPI output fixes: The JSON designer validates fields, paths, and operations, and generated OpenAPI documents now resolve $ref references correctly and produce valid YAML output.
  • Dashboard activity details scoped to the right connector: Activity details on the dashboard no longer list configuration fields belonging to a different connector type as if they were settings of the changed node.

Health Check​

New Features​

  • Platform information stays current automatically: Health Check now re-collects the platform's environment and version information every hour and re-syncs it to the license server, instead of only once at startup. Version details that were unavailable while other services were still booting (previously shown as "N/A" until a restart) now fill in on their own, and the license server no longer keeps a stale record.

Bug Fixes​

  • Health Check starts reliably in production with default settings: A default context-path value in the production configuration caused the Health Check service to fail at startup when no custom context path was configured. The default is corrected and root-path handling in internal URL building is fixed, so the service boots cleanly out of the box.
  • Deployed integrations show their configured public endpoint again: The legacy BACKEND_HTTP_ENDPOINT setting is honored again as the inherited display URL, so installations that rely on it see their configured public endpoint address for deployed integrations instead of an empty value.

1.18.4 is a stable release. Previous: 1.18.3