Using Freemarker templates, it is now possible to define the measurement payload format and the body of the responses managed by the Internet of Things Edge Platform REST.

Measurement timestamp management has been extended on Internet of Things Edge Platform REST and MQTT and on Internet of Things Gateway Cloud REST and MQTT in order to support the ingestion of a measurement message containing a special property named '_time', not modeled in the capability.

Internet of Things Edge Platform MQTT now supports the ability to set up custom certificates for publishing secure transports.

Internet of Things Edge Platform REST now supports the ability to set up custom certificates for endpoint publishing.

A new section has been added in the documentation of Internet of Things Gateway Cloud and Internet of Things Edge Platform to describe how the online/offline status of the devices is managed and determined. Please refer to Device Vitality Algorithm for more details.

New API GET "tenant/<tenantId>/devices/<deviceId>/authentications/clientCertificate/listRevoked" gets the list of non expired revoked certificates on Device Management. Please refer to Device Management API documentation for usage information.

The list certificate API GET "/tenant/<tenantId>/devices/<deviceId>/authentications/clientCertificate" on the Device Management can be paginated by providing skip and top values. If used without the skip and top values, the API will return all the entries. Please refer to Device Management API documentation for more information.

A new section has been added to list revoked certificate API with recommendations on usage of the certificate creation and revocation. Please refer to Access Revoked Device Certificates and Renew a Device or Gateway Certificate for details.

Resolved an issue on Internet of Things Gateway Cloud MQTT and Internet of Things Edge Platform MQTT that could prevent the MQTT connection from closing when the device was deleted.

Improved format of stored messages for buffering feature on Internet of Things Edge Platform, allowing better memory management and reducing the possibility of having an OutOfMemory exception in particular scenarios.

The Internet of Things Service Cockpit was enhanced with new options for sensor filtering and pagination. For more information, please refer to section Inspect a Sensor in the Internet of Things Service Cockpit documentation.

The Device Management swagger will contain V2 APIs on PEM certificate creation for device, gateway and tenant.

Service is implemented to remove expired certificate fingerprints from Device Management every day. Hence the API to list the certificate fingerprints will return only the fingerprints which are not expired.

The GET users' response will contain the locked timestamp as well.

Resolved an issue that prevented an online device from displaying correctly while using router certificates with the Internet of Things Gateway Cloud MQTT.

Resolved an issue that could reset the default name of the Internet of Things Edge Platform.

Capability PUT API in swagger UI for Device Management will show only the alternateId and name that can be modified.

The Device Management APIs will return HTTP 404 instead of HTTP 500 for invalid URL request.

Resolved an issue that could prevent the correct behavior of the device certificate revocation on Internet of Things Gateway Cloud and Internet of Things Edge Platform.

Simplified the way to send data to the Internet of Things Edge Platform REST with the secure transport, making the procedure uniform to that for sending data to the Internet of Things Gateway Cloud REST.

Resolved an issue that, in case of 'Stealing Link' error, could prevent Internet of Things Edge Platform MQTT and Internet of Things Gateway Cloud MQTT from properly managing device status, showing devices offline despite sending data.

Tenant admin will be able to revoke the certificate of the tenant devices using the API "/devices/{deviceId}/authentications/clientCertificate/{fingerprint}".

The Internet of Things Service Cockpit was enhanced with a new version of SAP UI5 v.1.71.

Documentation related to Buffering on the Internet of Things Edge Platform has been revised.

Added tenant ID to the processing message format as described in Processing Message Format.

Starting from Release 4.58.0, the minimum required version of the java runtime environment for the Internet of Things Edge Platform is 1.8.0_192.

Enhanced audit logging of security events on Internet of Things Gateway Cloud and Internet of Things Edge Platform.

Enhanced audit logging on Device Management and Message Processing.

Resolved an issue for maintaining order of capability properties on gateway synchronization.

Enhanced the Internet of Things Service Cockpit in the Message Processing HTTP URL configuration to support 512 characters. For more information, please refer to Configurations.

Enhanced the Internet of Things Service Cockpit in the Message Processing HTTP Header configuration template, for reference on how to create sensitive headers. For more information, please refer to Configurations.

Resolved an issue in the Internet of Things Service Cockpit, that was preventing the full visualization of instance and tenant users.

Updated a third-party library that may prevent Internet of Things Gateway Cloud REST and Internet of Things Edge Platform REST from working as expected.

Message Processing /tenant/{tenantId}/services/{serviceId}/schemas/{version}/configurations API has been enhanced by adding an additional field to the HTTP headers which does not allow sensitive headers to be returned in the response. For more information, please refer to HTTP Processing Service.

Resolved an issue in the Internet of Things Service Cockpit, where the configurations and selectors for message processing were visible only for the users with the Role Administrator. From now onwards, the users with the Role User will be able to access these information in read-only mode.

Updated the CXF library to address security vulnerabilities.

Netty is now being used to expose the Rest endpoint on the Internet of Things Edge Platform. Please refer Help Portal for details on the configuration changes.

Strengthened the internal transport used on the Internet of Things Edge Platform thereby improving the communication security.

Resolved an issue in the Internet of Things Service Cockpit, where everytime there was a connection issue with the backend, the Data Visualization was showing the message "No data found. Please consider choosing a different time range." From now onwards, a complementary warning message to verify the connection or to retry later, will be shown.

Resolved an issue in the Internet of Things Service Cockpit, where the message "The user is locked" was shown everytime a user tried to execute any action with no required permission in the backend. From now onwards, an appropriate message, returned by the backend API, will be shown.

Optimized the message ingestion by adding retries for failed messages.

Updated the Security Recommendations and Data Protection and Privacy sections in the Security documentation.

Exposed unlock user API on Swagger.

Resolved an issue that could prevent the Internet of Things Edge Platform from correctly managing measurements after changing the SensorType of a Sensor.

Resolved an issue in the Internet of Things Service Cockpit, where the Data Visualization 2D chart lines were broken by non-complete measures (for capabilities with more than 1 property) for a particular timestamp.

Added validation to make sure that Capability cannot have more than one date type property.

Validation to check command properties must have only the properties configured to the capability.