Skip to content

Release Notes 2026.2.0-rc1


Overview

The certificates of private keys can now be renewed automatically via ACME. The security tab of a node and Access Control check the rights of the user more strictly, and every installation of the API Gateway Manager gets its own TLS certificate.

New Features

  • Automatic certificate renewal via ACME

    • New integration "ACME" for any ACME compatible server, e.g. Secardeo certACME, EJBCA or step-ca, also with External Account Binding

    • "Renew now" and a daily automatic renewal per private key in the security tab of a node. The private key stays on the gateway, optionally a new key is created on every renewal. Afterwards the listen ports using the key are restarted (gateway 11.2.1 or newer)

    • DNS-01 challenge via the new integration "DNS (RFC 2136)"

    • Problems are shown as advices and can trigger notifications via automations

    • See Integration: ACME

  • Configuration, tab TLS Certificate: shows the TLS certificate of the API Gateway Manager itself and warns 30 days before it expires. See Your own TLS Certificate.

  • "Create New Private Key" uses Graphman on gateways 11.2.0 or newer.

  • Push to Git: branch and tag can be entered in the push dialogs.

Changed

  • Private keys are exported as PKCS#12 file protected with a password that you enter in the export dialog.
  • Faster page loads, and a considerably faster Access Control.

Security and Maintenance

  • All changes in the security tab of a node require write rights on the environment of the node and of every target.
  • Private keys are no longer left unprotected on the server when they are exported or copied to several targets.
  • Access Control is only available to administrators and users with the permission group Manage Users. Users with Manage Users can not change administrators or give anyone the permission group Administrator. All changes are protected against cross-site request forgery (CSRF).
  • Without your own TLS certificate, every installation creates its own self-signed certificate on the first start. Before, all installations used the same private key. After the update, browsers and clients ask once to accept the new certificate. See Your own TLS Certificate.

Bug Fixes

  • The export dialog of private keys failed with error 500.
  • After a restart of the container (e.g. docker restart), the API Gateway Manager could fail to start with "httpd (pid ...) already running".

Requirements

  • ACME: gateway 11.1.1 or newer. The ACME server must be reachable via HTTPS and authorize the domains without a challenge (e.g. External Account Binding) or via DNS-01. HTTP-01 and TLS-ALPN-01 are not supported.