Changelog and Upgrade Guide

What has changed in 0.33.1?

Fixed

  • an issue regarding proper path rewriting for Service-Containers allowing inbound http(s) connections

  • an issue api with wildcard permissions not including the direct parent

What has changed in 0.33.0?

Added

  • a new protocol: Heidenhain TNC, giving access to several CNC machine types

  • possibility to deploy the connectware as virtual or physical appliance

  • increased security measures by using more restrictive content security policies (CSPs)

  • moved to TLS1.2

  • dynamic configuration possibility of our ingress controller, allowing seamless integration of HTTP or even TCP based third-party applications within services

  • an easy-to-use install script available under: https://download.cybus.io/connectware-online-installer-0.33.0.sh

Changed

  • self-signed certificates are generated automatically during connectware upstart

  • the default IP range has been moved to 172.X.X.X/24 to improve compatibility with company networks. NOTE: As a result existing .env files have to be adapted.

Fixed

  • an issue with overflowing text in snackbar notifications

  • an issue of not being able to delete containers that got stuck in a restart loop

  • a sorting issue w.r.t. log message display

Important

Before installing make sure:
  • possibly existing .env file is deleted in the targeted install folder

  • possibly existing docker volumes with name connectware_certs are deleted

What has changed in 0.32.0?

Added

  • an option to handle retained messages in the DeviceMapper for MQTT connections (forwardRetained)

  • full documentation of the OPC-UA protocol (see OPC-UA)

  • possibility to install the Connectware via a single script (prerequisites are a linux based OS having docker and docker-compose installed)

  • a new User panel, allowing to manage users, set roles and access permissions (see User Management for details)

  • possibility to specify device names on individual instances (see Commissioning file structure)

  • Beta feature for client-registration (see Self Registration)

Changed

  • the authentication and authorization scheme for both - the REST-ful management API and the MQTT-based data API.

    • Authentication now supports basic (password based), token (JWT based), and client-certificate methodology.

    • Authorization, i.e. access permissions can be generically formulated for both, individual REST-ful paths and MQTT topics. A set of permissions can be combined into named roles , ready for sharing with other users (see Add role to user).

  • the output format of the OPC-UA protocol. It now provides the data in the standard format (being {"value": "<value>", "timestamp": "<msSinceEpoch>"})

  • the output format of the MODBUS protocol. It now provides the data in the standard format (being {"value": "<value>", "timestamp": "<msSinceEpoch>"}).

    • NOTE: The new format is only enabled once the additional dataType property is provided with the commissioning file (see Modbus/TCP), else the behavior is unchanged.

  • the notification snackbars in the UI, they are now color-coded, categorized and perform stacking in case they appear shortly after each other

  • the logging panel in the UI, it provides a much clearer design and an improved filtering using chips for selecting log-categories, containers, etc. (see System)

  • the rendering of tabs in the UI, they are not spanning the full-width anymore but are more browser-like in look & feel

Removed

  • the Grantee and Permissions panel in the UI (got replaced by new User panel)