Everyware Cloud Developer's Hub

Everyware Cloud (EC) is an IoT Integration Platform distributed and supported by Eurotech. Based on Eclipse Kapua, Everyware Cloud offers an open and modular IoT Cloud Platform based on a micro-services architecture. Everyware Cloud provides device management, diagnostics, provisioning, remote access of IoT gateways and devices and integration services for the telemetry data.

Get Started

Release Notes

📘

Eurotech recommends the latest patch release for most environments.

Everyware Cloud 5.8.3 Release Notes

Everyware Cloud 5.8.3 components:

  • Admin Console 5.8.3
  • RESTful API 5.8.3
  • Events Broker 5.8.3
  • Messaging 5.8.3
  • VPN 5.8.3

Everyware Cloud 5.8.3 is based on Eclipse Kapua 1.4.4 and includes all changes from earlier Everyware Cloud versions.

New Features

Everyware Cloud 5.8.3 introduces the following new features:

Improvements

Everyware Cloud 5.8.3 introduces the following improvements:

  • Various security fixes

Everyware Cloud 5.8.2 Release Notes

Everyware Cloud 5.8.2 components:

  • Admin Console 5.8.2
  • RESTful API 5.8.2
  • Events Broker 5.8.2
  • Messaging 5.8.2
  • VPN 5.8.2

Everyware Cloud 5.8.2 is based on Eclipse Kapua 1.4.3 and includes all changes from earlier Everyware Cloud versions.

Bug Fixes

Everyware Cloud 5.8.2 fixes the following bugs:

  • Device Provisioning will fail when at least one job has been executed at least ones on the specific account

Everyware Cloud 5.8.1 Release Notes

Components

Everyware Cloud 5.8.1 components:

  • Admin Console 5.8.1
  • RESTful API 5.8.1
  • Events Broker 5.8.1
  • Messaging 5.8.1
  • VPN 5.8.1

Everyware Cloud 5.8.1 is based on Eclipse Kapua 1.4.2 and includes all changes from earlier Everyware Cloud versions.

Improvements

Everyware Cloud 5.8.1 introduces the following improvements:

  • Introduced a customisable JSON converter for REST routes
  • Introduced a new variable (containerConsole.env.openIDConnect.provider.adfs.userIdCustomClaim) that can be set to use a different JWT claim instead of the sub claim to match the user in ADFS authentication
  • Several security and performance improvements

Bug Fixes

Everyware Cloud 5.8.1 fixes the following bugs:

  • Route names can now be reused outside a single Account
  • Fixed resource leak caused by an internal network connector
  • Connections are now correctly cleaned up from the provisioning account after a successful provisioning operation

Everyware Cloud 5.8.0 Release Notes

Components

Everyware Cloud 5.8.0 components:

  • Admin Console 5.8.0
  • RESTful API 5.8.0
  • Events Broker 5.8.0
  • Messaging 5.8.0
  • VPN 5.8.0

Everyware Cloud 5.8.0 is based on Eclipse Kapua 1.4.0 and includes all changes from earlier Everyware Cloud versions.

New Features

Everyware Cloud 5.8.0 introduces the following new features:

  • Elasticsearch has been upgraded to 6.8.7. After upgrading from a previous version of Everyware Cloud, it's necessary to run the Elasticsearch Migration Tool in order to migrate the data to the new index format

Improvements

Everyware Cloud 5.8.0 introduces the following improvements:

  • Specific account settings can now be changed within the same account (e.g. Credential Service Lockout Policy and Minimum Password Length).
  • Multi Factor Authentication Trust Duration for Devices can now be changed
  • Dynamic Routes can now be configured for Log Messages

Bug Fixes

Everyware Cloud 5.8.0 fixes the following bugs:

  • Provisioning Request Dialog shows an error due to a missing permission
  • Log View reporting an error due to a wrong permission name
  • Deleting a Provision Request returns an error
  • An error is returned when authentication to REST APIs with an API Key
  • Kafka dynamic routes don't assign messages to correct Kafka partitions
  • REST dynamic routes ignore URL Options field
  • Routes are blocked because of an high inflight messages count
  • VPN container not starting correctly

🚧

Single Sign-On Breaking Change

Please note that the OpenID Connect callback servlet address for the Single Sign On is now /openid/callback instead of /sso/callback. Any OpenID Connect Provider configuration already in place should be changed accordingly.

Updated 18 days ago

Release Notes


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.