SOAP-to-REST release notes

This release introduces a quality-of-life improvement for platform operators, making it easier to access release notes for the currently running platform version.

New Features

Release Notes Link for Current Version

A Release notes link is now available on the Current platform card, located on the Settings → Updates page in the user interface.

This feature allows platform operators to review the release notes for their currently installed and running version at any time. This is particularly useful for verifying features or changes associated with the current version, even when the system is fully up-to-date and no new updates are available.

To access the release notes for your current version:

1. Navigate to Settings.
2. Select the Updates page.
3. On the Current platform card, click the Release notes link.

This release streamlines the configuration of trusted proxies and resolves an issue with proxy hop resolution in Google Cloud Platform (GCP) environments.

Changes

• Streamlined Trusted Proxy Configuration: The system now automatically initializes the trusted proxy declaration in the background. This removes the need for API publishers to perform the manual "Enable broker" setup step. As a result, the setup banner clears automatically without user intervention.

Fixes

• GCP Trusted Proxy Hop Resolution: Resolved an issue where trusted proxy hops failed to resolve automatically on Google Cloud Platform (GCP) deployments if the load balancer flavor was not explicitly defined. Proxy hops now resolve automatically for all GCP deployment configurations.

This release provides a fix for an issue affecting the import of WSDL and XSD documents.

Fixed Issues

This section details the issues resolved in this release.

WSDL and XSD Import Failures due to Byte Order Mark

An issue was resolved where importing a WSDL or XSD document from a URL would fail.

• Symptom: The import process would terminate with a Content is not allowed in prolog error.
• Cause: This error occurred if the source file contained a UTF-8 Byte Order Mark (BOM). The presence of a BOM is common in files served by certain web servers, such as Microsoft IIS.
• Resolution: The import process now automatically detects and removes the UTF-8 BOM from WSDL and XSD files during import. This allows the service onboarding to complete successfully without requiring manual modification of the source files.

Summary

Version 1.7.9 is a maintenance release that addresses issues related to dashboard metrics and user interface stability.

Fixed Issues

This release includes the following fixes:

• Accurate Dashboard Metrics: Corrected an issue where the "Calls / day · discovered" card on the Operations Dashboard displayed an inflated count of discovered services. The calculation now correctly uses a 24-hour window, ensuring the metric accurately reflects the number of active discovered services.

• Table Sorting and Filtering Stability: Resolved an issue where table filters, such as checklist and condition filters, were unstable.

Overview

Version 1.7.8 introduces new security controls, simplifies network configuration, and resolves an issue with SOAP testing visibility. Key changes include the ability to define IP-based access restrictions on a per-service basis and the automation of trusted proxy configuration, which removes a manual setup step.

New Features

Per-Service IP Address Access Control

API publishers can now configure access controls for individual services based on the caller's source IP address. During the service onboarding flow or from the individual service settings page, you can define a list of allowed source IP addresses. Alternatively, you can configure the service to be "open, no limit," which does not restrict access by IP.

Changes and Improvements

Automated Trusted Proxy Configuration

The platform now automatically detects and configures trusted proxies based on the deployment's infrastructure topology. This enhancement removes the need for manual configuration of trusted proxies in the global settings menu. A primary benefit of this change is the prevention of connection rejections that could previously occur in development environments due to misconfiguration.

Fixes

Manual SOAP Test Payload Visibility

This release corrects an issue in the Manual SOAP Test feature. Previously, when using JSON input for a manual SOAP test, the "SOAP Request Sent" tile in the user interface was disabled and marked as "Not available," even on successful requests.

The tile is now correctly enabled and clickable for all outcomes, including successful runs and SOAP faults. This allows API publishers to inspect the exact generated SOAP envelope that was sent, which aids in troubleshooting and validating the transformation from JSON to SOAP.

Summary

Version 1.7.7 introduces a new SOAP Broker mode for handling legacy SOAP integrations and an associated access control mechanism based on consumer IP addresses.

New Features

This release adds the following capabilities.

SOAP Broker Mode

A new "SOAP Broker" mode is now available. This mode provides transparent, byte-faithful SOAP-to-SOAP passthrough. It is designed for legacy integrations where preserving the integrity of the original XML payload is critical.

SOAP Broker Access Control

To secure services operating in SOAP Broker mode, this release adds IP-as-credential access control. API publishers can create grants that restrict service access to a list of authorized API consumer IP addresses.

Version 1.7.6

This release introduces significant improvements to the F5 Bulk Apply feature, enhancing its resilience, reporting, and user interface. It also retires the internal documentation self-upload pipeline in favor of a centralized platform.

Changed Features

This release includes the following changes.

F5 Bulk Apply HTTP Profile Semantics

The behavior for applying HTTP profiles in bulk to F5 virtual servers has been modified to prevent failures when a profile of the same type already exists.

• Previous Behavior: The operation would fail with F5 API error 01070097 (duplicate profiles) if a virtual server already had an active HTTP-type profile.
• New Behavior: The process now uses replace semantics. It first detaches any existing, non-matching HTTP profile from the virtual server before attaching the new one. This change avoids the 01070097 error and allows for smoother profile updates.
• Scope: This change only affects HTTP-type profiles. Other profile types, such as SSL and TCP, remain untouched during this operation.

F5 Bulk Apply Resilience and Reporting

The bulk apply process has been made more resilient to individual failures, and the API response provides more granular status details.

• Failure Handling: Instead of aborting the entire batch upon encountering an error with a single virtual server, the process now records the failure for that specific server and continues with the rest of the batch.
• API Response: The API response for a bulk apply operation now includes:
  • failedCount: The number of virtual servers that failed to update.
  • failureReason: A message detailing the cause of failures.
• Overall Status: The operation now returns an overall status of failed only if two conditions are met: 1) no virtual servers were successfully updated, and 2) at least one virtual server encountered an error.

F5 Bulk Apply User Interface

The admin user interface for the F5 Bulk Apply feature has been updated to provide clearer and more persistent feedback.

• Status Display: Bulk apply outcome messages are now displayed on the persistent f5ScopeStatus line, rather than the previous hidden legacy scan panel.
• Detailed Outcomes: The UI now reports a detailed summary of the operation, such as "X updated, Y already set, Z failed".
• Error Surfacing: When a failure occurs, the backend failureReason is now displayed in the UI.
• No-Op Handling: Operations that result in zero changes (0 updated / 0 total) are now treated as warnings instead of silent successes.
• Modal Behavior: In the event of any failure during the bulk apply process, the configuration modal will now remain open to allow for review and correction.

Documentation and Pipeline Retirement

The internal pipeline for self-uploading product documentation has been retired to streamline content delivery.

• New Process: All product documentation now flows exclusively through the Specaria platform's version-cut-over event.
• Retired Components:
  • The manual operator script scripts/upload-specaria-docs.ps1 has been deleted.
  • The cloudbuild-specaria-docs.yaml file has been replaced with a minimal no-op stub. This prevents out-of-repository Cloud Build triggers associated with v* tags from failing.
  • The SPECARIA_DOC_API_KEY environment variable and its related endpoints are retired and have been marked as such in documentation.
• IAM Updates:
  • The secretAccessor role is now granted to the active consumer service account (s2r-admin-api-sa@<project>.iam.gserviceaccount.com). It was previously granted to a historical Cloud Build service account.
• Documentation Placeholders:
  • Hardcoded project references in docs/integration/specaria-values.md have been replaced with the generic placeholder <deployment-project-id>.

Summary

Version 1.7.1 introduces significant usability enhancements to tables within the administration interface. This release adds advanced, Excel-style column filtering and allows for personalizing table layouts by reordering and resizing columns. Additionally, all tables have been updated to be fully responsive, improving the user experience on various screen sizes.

New Features

Advanced Column Filtering

Tables throughout the administration interface now support advanced filtering capabilities. To access these filters, right-click a column header to open a popover menu.

The filtering options include:

• Value-based filtering: Search for and select specific values from a list, including an option to filter for blank entries.
• Condition-based filtering: Apply type-aware conditions. Supported conditions include text, number, and date range filters, such as "Between".

Customizable Table Columns

Users can now customize the layout of tables to suit their preferences. The following customizations are available:

• Column Resizing: Drag a column header's edge to resize its width.
• Column Reordering: Drag and drop a column header to a new position.

These layout preferences are saved automatically for each table. A "Reset" option is available to restore the table to its default column layout.

Changes and Improvements

Improved Table Layouts

All administration tables have been upgraded to be fully responsive. Tables now automatically adjust their width to fit the screen, which prevents horizontal scrolling. To maintain a clean layout, long text content, such as URLs or file paths, is now truncated with ellipses.

Summary

Version v1.6.21 addresses issues related to the platform's update mechanisms. This release improves the reliability of tracking product update history and ensures that automated system service updates execute correctly.

Fixes

This release contains the following fixes:

• Update History Status: Resolved an issue where product update records could indefinitely remain in an "in progress" state. The system's update operations now track each attempt individually, ensuring the update history accurately reflects the final outcome, such as success, failure, or rollback.
• Automated System Service Updates: Fixed a problem where background management services were unable to discover and apply system self-updates. This was caused by mismatches in update channel and versioning data. Automated updates now execute in the background without requiring manual intervention.

Overview

Version 1.6.20 introduces enhanced control over the software update process, particularly for deployments requiring manual approval. Administrators can now review and apply available updates on-demand. This release also improves the visibility of the current update status and fixes an authentication issue related to manual update requests.

New Features

Manual Software Update Control

For deployments configured with a manual approval mode, an "Apply Update" option is now available in the settings interface. This feature allows administrators to:

• Review available software releases before installation.
• Trigger the update process at a time of their choosing.

This change gives administrators direct control over the update lifecycle, ensuring that updates are only applied after explicit confirmation.

Enhanced Update Status Display

The software update status display has been improved to provide more context. It now shows:

• The latest available product version.
• The currently configured update mode (automatic or manual).
• The configured interval for checking for new updates.

Changes

Update Mode Enforcement

The behavior of different update modes is now more strictly enforced:

• Manual / Operator Approval Mode: Deployments configured for manual approval will now detect and display available updates but will not install them automatically. Installation only proceeds when an administrator uses the "Apply Update" option.
• Automatic Mode: This mode's behavior is unchanged. It continues to install updates as soon as they become available.

Fixes

This release corrects an issue with request authentication signatures. This bug previously prevented manual update requests, initiated by an administrator, from being processed successfully. With this fix, the "Apply Update" feature functions as intended.

This document provides the release notes for version 1.6.19.

Changes in This Release

This release introduces an improvement to the update check mechanism and clarifies user interface text.

On-Demand Update Checks

The behavior of the Check now button in the Settings > Updates menu has been changed. Previously, clicking this button would refresh the view with cached data. Now, it immediately initiates a live, on-demand check for both software and topology updates, retrieving the latest available status directly from the update source.

UI Text Improvements

The inline documentation and help text within the Settings menu have been updated for improved clarity.

Version 1.6.18 introduces enhancements to the automated update check mechanism and the user onboarding experience, along with important bug and security fixes.

Changes

This release includes the following enhancements and behavioral changes.

Automated Update Check Preferences

Automated update checks now correctly honor the preferences configured by the API publisher. The system will respect the settings for:

• Update channel
• Update mode
• Update check frequency

Onboarding UI Improvement

To streamline the initial setup process for new users, the Conversion Overrides panel within Step 3 of the onboarding workflow is now collapsed by default. API publishers can still expand this panel to access its settings when needed.

Fixes

This release addresses the following issues.

UI and Display Fixes

• A rendering issue during onboarding has been fixed. Previously, opening the version update menu would cause it to appear behind the main navigation ribbon, obscuring it from view.

Security Fixes

• A security vulnerability on the update settings page has been resolved. The system now validates all release note links to ensure they are not malicious, preventing the potential for script execution.

Summary

Version 1.6.17 is a patch release that addresses a bug affecting the display of software updates.

Fixed Issues

This release resolves an issue where the Settings > Updates page could incorrectly display a false error banner and an empty list of available updates.

• Symptom: Users would see an error message stating "A received update was rejected because its signature didn't verify" and the list of available updates would be empty, even when updates were available.
• Resolution: The system now correctly verifies update availability and status. The Settings > Updates page accurately reflects the system's release state without displaying erroneous signature verification errors.

This release introduces a new background observation capability and includes important fixes for the automatic update mechanism and security vulnerabilities in underlying dependencies.

New Features

• Background Network Topology Observation: This version enables the platform to observe network topology in the background. This process is secured using embedded cryptographic key verification.

Fixes and Improvements

• Automatic Update Validation: A signature verification issue has been resolved. This issue previously prevented automatic background updates from being correctly validated and applied.
• Dependency Security: Addressed security vulnerabilities within underlying software dependencies. These fixes mitigate potential risks, including privilege escalation and denial-of-service (DoS) attacks.

Breaking Changes

There are no breaking changes in this release.

Version 1.6.15 is a maintenance release that improves the system's update mechanism and corrects an issue with version reporting. This release focuses on operational stability by ensuring that deployments can accurately detect new releases and that system status reports reflect the true installed version.

Improvements

• Enhanced Product Update Accuracy: The system update check, located under Settings > Updates, now automatically resolves the correct update channel assigned to the deployment. This ensures that newly published releases for the assigned channel are reliably detected.

• Improved Update Detection with Unknown Version: If the system is unable to determine its currently installed version during an update check, the updates panel will now display an alert that an update may be available. Previously, this scenario could cause the system to incorrectly report that it was up to date.

Fixes

• Accurate System Version Reporting: System status views and health reports now consistently display the correct release version number. This resolves an issue where a generic development placeholder was sometimes shown instead of the true version.

Breaking Changes

The source does not indicate any breaking changes in this release.

Upgrade Instructions

The source does not specify any special migration steps for this version. The standard update process applies.

Summary

Version 1.6.14 introduces automatic health heartbeats for improved operational visibility of self-identified deployments. It also simplifies deployment management by standardizing on a single container image per version, with configuration now resolved dynamically from the central platform.

Added

Automatic Deployment Heartbeats

Self-identified installations now automatically transmit health heartbeats to the central management platform. This provides API publishers with continuous visibility into the connectivity and operational status of their deployed agents. This feature addresses the need for real-time health monitoring.

Changed

Unified Deployment Container Images

Release deployments have been standardized to use a single container image per version. Previously, different deployment configurations may have required specialized image variants or local environment configuration.

With this change, all deployment-specific configuration is resolved dynamically by the agent at runtime via the central management platform. This eliminates the need for API publishers to build or maintain multiple container images.

Fixed

Deployment Status Visibility

This release fixes an issue where self-identified installations failed to report telemetry to the platform. This failure prevented the "last seen" timestamps and the online connectivity status from updating correctly in the management interface. The fix ensures that the status of all deployments is accurately reflected.

This document provides the release notes for version 1.6.13.

Added

Automated Topology Reconciliation

The release controller can now automatically fetch, verify, and apply system network topology configurations. This feature synchronizes load balancer path rules and access controls with their desired state, reducing manual configuration management.

Built-in Update Verification Keys

Release verification keys are now pre-packaged within the release controller. This change eliminates the need for manual key provisioning during the deployment setup process.

Changed

Accurate Release Controller Status Reporting

The status reporting mechanism on the Settings page has been updated. A release controller that is operating correctly but has self-updates disabled will now accurately reflect a healthy operational status, instead of incorrectly displaying a degraded state.

Fixed

Settings Panel UI Formatting

This release restores the proper layout, spacing, and typography for key-value labels and details within the Updates and License tabs of the Settings panel.

Overview

Version 1.6.12 introduces enhancements to license visibility, streamlines the license management interface, and improves the reliability of automated updates and system status checks.

Enhancements

• Expanded License Details: The License settings page now displays the deployment type and the assigned update channel in addition to the active license information.

Changes

• Streamlined License Interface: The License settings page has been updated to align with automated license delivery. Obsolete steps for manual license requests have been removed. The "Issued to" field now displays the recipient's email address.
• Internal Release Channel Support: The system now correctly performs update checks and tracks status when subscribed to the internal update channel. This ensures that system update status is accurately reported in the management console.
• Automated Service Status Discovery: System status checks for update-related components are now dynamically routed through an internal load balancer. This change removes the requirement for hardcoded status configuration settings.

Fixes

• Automatic License Identity Reconciliation: A fix has been implemented to resolve an issue where mismatched deployment identity records could lead to repeated license validation failures during automated background updates.
• Missing License Information: An issue has been resolved where the "Issued to" field on the License summary card would appear blank when displaying an active license.

Summary

Version 1.6.11 focuses on improving the administrative experience for software updates and license management. This release introduces automatic notifications for background updates, provides more detailed license status information, and streamlines the user interface for both updates and offline license activation. Key fixes address issues with deployment ID consistency and extraneous log errors.

New Features

Automatic Update Notifications

System updates that complete in the background are now recorded in the update history. This change also triggers administrative notifications, providing administrators with full visibility into all software updates as they occur.

Expanded License Details

The license settings page has been enhanced to display additional status indicators. These new indicators include the current offline operation status and the number of remaining days in any applicable grace period.

Changes and Improvements

Reorganized License and Update Settings

To create a more intuitive administrative workflow, several controls and information points have been relocated:

• Deployment ID: This information is now located on the License page instead of the Updates page.
• Offline License Management: Controls for managing offline licenses have also been moved from the Updates page to the License page.

Streamlined Updates Interface

The platform updates summary view has been simplified for clarity. Redundant "channel" and "mode" entries have been removed. The interface now provides clearer status messages when the system is checking for available updates.

Simplified Offline License Activation

The workflow for offline license activation has been updated to prioritize direct token input. This change is designed to make the activation process easier for deployments in air-gapped or network-restricted environments.

Fixes

Unified Deployment Identification

This release resolves an issue where background management services and application endpoints could generate mismatched deployment identifiers. This fix prevents license validation failures and incorrect reports of offline status that were caused by the identifier mismatch.

Extraneous Log Errors

An obsolete background update check that was generating redundant HTTP 404 error entries in application logs has been removed. This change reduces log noise and eliminates misleading error messages.

Summary

Version 1.6.10 improves security by changing how mTLS certificates are stored and resolves a bug that prevented the import of WSDL definitions.

Changes

Enhanced mTLS Certificate Security

Product mTLS security certificates are now embedded directly into the service binaries. Previously, certificates were stored as standalone files within deployment images. This change improves the protection of the underlying authentication credentials.

Fixes

WSDL Import Failures

This release resolves an issue where importing WSDL (Web Services Definition Language) definitions would fail. The failure was caused by errors during XML transformation and parsing.

This release enhances the security and reliability of the software update delivery mechanism.

Summary of Changes

This version introduces the use of dedicated authentication certificates for each product when publishing software updates. This change isolates the update process per product, strengthening the integrity and verification of delivered software releases. No action is required to enable this feature.

Changes in This Release

Changed

• Software release updates are now published using dedicated, per-product authentication certificates. This improves the security and reliability of the update delivery process.

These are the release notes for version 1.6.7.

Summary of Changes

This release introduces new capabilities for on-demand service health testing and expands support for service discovery from a wider range of traffic sources.

Added

This section details the new features introduced in this release.

Manual and Automated Conversion Replay

This release adds a mechanism to test the round-trip conversion health for individual services. This can be triggered in two ways:

• Manual Trigger: A new button in the Services management console allows API publishers to initiate a health check for a service on demand.
• Automated Schedule: Health checks are now run automatically on a nightly schedule to ensure that service health indicators remain up to date.

Vendor-Agnostic Service Discovery

Service, consumer, and topology discovery capabilities have been expanded to support traffic sources beyond F5. The platform can now discover endpoints and learn schema fields from the following sources:

• Citrix
• HAProxy
• NGINX

This release provides fixes for WSDL parsing, traffic log viewing, and service deletion.

Fixed Issues

This release resolves the following issues:

• WSDL Schema Resolution on HTTP Redirects: WSDL documents that import schemas from URLs are now processed correctly when the server issues an HTTP redirect. The platform now resolves relative XML schema import paths against the final destination URL after the redirect, which prevents WSDL parsing failures.

• Traffic Log Detail Display: An issue causing an HTTP 500 server error when viewing the details of a traffic log entry has been resolved. This error occurred specifically for transactions that contained request or response headers.

• Service Deletion Stability: Resolved a condition where deleting services with a large volume of associated historical traffic logs could lead to database deadlocks, timeouts, or system lock contention. The deletion process is now more stable and resilient under these circumstances.

Overview

Version 1.6.5 introduces a significant simplification for deployments on Google Cloud Platform, enhances the performance of the Operations Dashboard, and resolves a key API error. This release focuses on improving operational efficiency and user experience.

New Features

Automatic Deployment Configuration on Google Cloud Platform

System deployments on Google Cloud Platform (GCP) are now automated to detect key configuration details from the environment. This eliminates the need for operators to manually configure certain environment variables.

The system automatically detects the following:

• Environment project details
• Region
• Service templates
• Active product versions

This change streamlines the deployment process and reduces the potential for configuration errors on GCP.

Enhancements

Operations Dashboard Load Performance

This version includes a significant performance improvement for the Operations Dashboard. Load times have been reduced by optimizing how F5 summary data is handled. The system now retrieves and processes this data more efficiently in the background, resulting in a faster experience for operators monitoring the system.

Resolved Issues

Service List API Error

A bug has been fixed that caused an HTTP 406 error when listing services. This error occurred in both administration views and when using management endpoints. API consumers and administrators will no longer encounter this error when retrieving the service list.

Overview

Version 1.6.4 is a maintenance release that introduces new deployment flexibility, improves API consistency, hardens security for production environments, and resolves an authentication issue with system update checks.

Added

Customizable Relay Container Images

Relay deployment scripts now support specifying custom container image references. This allows API publishers to use images from private or alternative container registries instead of the default public registry. This customization is configured through environment variables.

Changed

Unified License Status Reporting

The API response fields for reporting system license status have been standardized. Previously disparate fields are now consolidated into a single, consistent property across all relevant API responses. This change simplifies the process for API consumers to programmatically track the system's license state.

Production Security Hardening

To provide a more secure initial installation, several development-only and legacy components have been removed from the platform. The following items are no longer included in a default deployment:

• Development-only authentication overrides
• Unused background schedulers
• Legacy default seed accounts

Fixed

System Update Authentication Failures

This release corrects an issue where background checks for system updates would fail with authorization errors. The underlying problem was related to stale credentials used during the polling process.

The fix implements a mechanism to automatically rotate and refresh the dynamic credentials used for these checks, ensuring that the update polling process remains authenticated and can successfully retrieve system update information.

Version 1.6.3 introduces significant enhancements to licensing, dynamic configuration, and authentication. Key changes include automatic administrator account provisioning, configurable license enforcement policies, and the replacement of static tokens with certificate-based authentication for product updates.

Added Features

Tenant Administrator Bootstrapping

Upon license activation, the platform now automatically provisions the primary administrator account for a new tenant. This allows an administrator to gain immediate access to the system to begin tenant setup and management without manual intervention.

Flexible License Enforcement Modes

This version introduces configurable license enforcement policies. One of the new options is a runtime stop policy, which will halt all service processing if the system detects that a valid license is expired or missing past its grace period. This provides a stricter enforcement mechanism for license compliance.

Changed Features

Certificate-Based Update Authentication

The mechanism for authenticating product update checks has been changed. The system now uses mutual TLS (mTLS) with client certificates and unique deployment identifiers for authentication. This change removes the previous requirement for API publishers to configure and manage static update registry tokens.

Dynamic Capacity Limit Metering

Capacity metering is now more dynamic. The system reads usage limits directly from the capabilities defined in the active license file. This allows for custom enforcement thresholds to be applied without requiring a product upgrade or restart.

License-Driven Capabilities

System functionality is now enabled dynamically at runtime based on the capabilities granted by the active license. This change removes the need to configure functionality using deployment environment flags, centralizing feature management within the license itself.

# Version 1.6.2

## Overview

Version 1.6.2 simplifies the integration of platform services by standardizing how they communicate. This release focuses on the product feedback and built-in AI Assistant features, removing the need for manual network configuration to enable them. The goal is to provide more secure and reliable communication for these services out of the box.

## Changes in this release

### Changed

*   The service integrations for the **product feedback** feature and the **built-in AI Assistant** have been standardized. This change ensures secure and reliable communication for these services without requiring manual network configuration.

## Upgrade Impact

After upgrading to version 1.6.2, any manual network configurations previously required for the product feedback and AI Assistant integrations are no longer necessary. The platform now manages these connections automatically. API publishers should remove any previous configurations to avoid potential conflicts and rely on the new standardized integration.

This release introduces significant enhancements to on-premises relay connectors, focusing on administrative control, security, and expanded network capabilities.

New Features

Version 1.6.0 includes the following new features.

Relay Connector Management and Security

API publishers can now manage on-premises relay connectors directly from the administration interface. This provides centralized control over connector lifecycle and security credentials.

Key capabilities include:

• Issuing Connector API Keys: Administrators can generate new, secure API keys for connectors.
• Revoking Connector API Keys: Existing API keys can be revoked at any time from the administration interface, immediately disabling the corresponding connector's access.

Bidirectional Relay Connector Capabilities

The functionality of on-premises connectors has been expanded to support bidirectional traffic flows, enhancing integration between central platform services and services running in a private environment.

How It Works

Connectors now include local proxy capabilities, enabling them to securely forward traffic originating from the on-premises environment to central services.

Simultaneously, security for traffic moving in the other direction has been hardened. When a central service sends a request to an on-premises backend via the connector, the connector restricts which hosts it is allowed to contact. This is enforced using a host allow-list.

The diagram below illustrates the bidirectional traffic flow managed by the relay connector.

flowchart TD
    subgraph "On-Premises Environment"
        B[Customer Backends]
        C[Relay Connector]
    end
    A[Central Services]

    C -- "Forwards traffic to" --> A
    A -- "Forwards traffic via" --> C
    C -- "Requests (restricted by host allow-list)" --> B

This release resolves issues related to automated system updates and health check monitoring.

Fixed

This version includes the following fixes:

• Automated Updates: Corrected a condition where automated system updates could fail or perform an unexpected rollback. This issue occurred when the update process encountered database migration tasks or services configured with relative health check URLs.
• Health Monitoring: Fixed an issue that caused deployment-time validation probes to fail for services. The failure was triggered by the presence of leading or trailing whitespace in the configured health check URLs. The system now correctly handles such whitespace.

This document provides the release notes for version 1.5.4.

New Features

Developer Role

This release introduces a new Developer role. This role is designed for team members who need to manage services without requiring full administrative privileges.

Users assigned the Developer role have permissions to perform the following actions:

• Manage service lifecycles
• Import WSDL definitions
• Manage service versions
• Configure conversion overrides
• View discovery data

This role allows for more granular access control, enabling developers to operate on services while restricting access to platform-wide administrative functions.

Fixes

Role Management Permissions

Previously, the ability to manage user roles was not exclusively limited to Administrators. This change ensures that only designated administrators can alter user permissions within the platform.