Release Notes for Previous Releases: ThingWorx Edge MicroServer (EMS) and Lua Script Resource (LSR)
The new features and the bug fixes that have been made for the various releases of the ThingWorx Edge MicroServer (EMS) are listed in the sections below. Starting with release 5.3.1, the IDs and SalesForce IDs for any issues that are fixed in this release are in a separate column (ID / SFID). The version(s) of the C SDK used by the version of EMS appears in parentheses in the table title.
To download the latest distribution bundle for your platform, visit the Software Downloads page of the PTC eSupport Portal, https://support.ptc.com/appserver/cs/software_update/swupdate.jsp.
Security
Releases of the ThingWorx Edge MicroServer (EMS) include security-related updates, as follows:
• Fixed potential security issues, including items proactively identified by vulnerability scanning software or PTC Quality Assurance testing. Please upgrade as soon as possible to take advantage of these important improvements.
• See this technical support article for important recommendations regarding the use and update of third-party software for ThingWorx.
Important Information
The EMS v.5.3.x releases are compatible with the v.8.5.x releases of the ThingWorx Platform. EMS v.5.4.0 through v.5.4.7 releases are compatible with the v.8.5.x releases of the ThingWorx Platform. These older EMS releases are not compatible with ThingWorx Platform v.9.2.1 and later, v.9.1.x, and v.9.0.2 and later v.9.0.x because they do not support SNI. In v.5.4.8, SNI support was added to the EMS, making v.5.4.8 and later versions of EMS compatible with ThingWorx Platform v.9.1.x and v.9.0.2 and later 9.0.x releases.
Certification with ThingWorx Platform for EMS v.5.4.9 and v.5.4.10 is as follows:
• EMS v.5.4.9 has been certified on ThingWorx Platform v.9.0.2 and later v.9.0.x releases..
EMS v.5.4.10 has been certified on ThingWorx Platform v.9.1.1.
While EMS v.5.4.9 and v.5.4.10 have not been certified on ThingWorx Platform v.9.2.1 or later, they should work with these later platform releases. Contact PTC Technical Support if you experience issues with ThingWorx Platform v.9.1.1 or later and the EMS v.5.4.8 or later.
It is strongly recommended to upgrade EMS to the latest version to ensure you have the latest security fixes. Use the latest EMS with ThingWorx Platform v.9.0.2 and later v.9.0.x, with v.9.1.1 and later v.9.1.x, and with v.9.2.1 and later v.9.2.x.
Click the title of the release notes version that you want to view. Click the title again to hide the content.
EMS and LSR, Version 5.4.10 (C SDK 2.2.12)
The 5.4.10 release of the EMS is built on release 2.2.12 of the ThingWorx Edge C SDK. This release provides an upgrade of SSL/TLS to v.1.1.1j.
In this release of the EMS, the property, fingerprint_whitelist has changed to fingerprint_allowlist. This feature was available in EMS v.5.4.8 and v.5.4.9. If you have used it in your applications and upgrade to v.5.4.10, you need to change the property name in the configuration file for your EMS.
EMS and LSR, Version 5.4.9 (C SDK 2.2.11)
The 5.4.9 release of the EMS is built on release 2.2.11 of the ThingWorx Edge C SDK. This release includes fixes for the following issues:
ID (SFID) | Description |
|---|---|
EDGA-2960 | When LSR 5.4.8 was started up using legacy AES encrypted strings, the encryption rollover failed to set the value in memory. As a result, the LSR attempted to use the wrong value. However, the correct value was persisted to the configuration file. Subsequent restarts of the LSR functioned as expected. This issue is fixed in this release |
EDGA-2963 | When the EMS or LSR was configured with an HTTP server that used a self-signed certificate, the connection from the client (for example, the LSR connecting to EMS) would be incorrectly rejected during certificate validation This issue is fixed in this release. |
EMS and LSR, Version 5.4.8 (C SDK 2.2.9)
The 5.4.8 release of the EMS is built on release 2.2.9 of the ThingWorx Edge C SDK. It includes a fix for CSDK-1781 where non-platform connections failed in EMS if a proxy server was used for the connection to ThingWorx Platform. Finallyl, it includes the enhancement in CSDK-1784, which adds support for host name validation.
The following table describes enhancements and issues fixed in this release of the EMS:
ID (SFID) | Description |
|---|---|
Enhancements | |
EDGA-2592 | Logging enhancements This release provides software changes to resolve the following issues: • Data was taking a while too be flushed to disk so that it appeared that nothing was being logged. • SDK log messages were not correctly intercepted so did not appear in the log after a restart. • Improve the processing of console-level and file-level logging. You can now set your file-level logging lower than your console-level logging. |
EDGA-2806 (15146278) | Authentication in Client Side Web Services EMS and LSR have a new data protection library that provides automated encryption of application keys, passwords, and other sensitive information in configuration files. Data is protected by a unique data protection key dp.dat that is automatically created by the EMS or LSR the first time it runs. Any existing encrypted data in configuration files is automatically converted to use the updated encryption method. PTC strongly recommends upgrading to this latest version of the EMS so that you have this and other security updates. |
EDGA-2849 (15146278) | Allows EMS to Load CA Cert File for Edge HTTP Client A new configuration option has been added to specify a list of CA certificates to validate HTTPS connections on the local area network. This enhancement allows you to have separate, distinct trust stores to use when validating HTTPS connections: one for the ThingWorx Platform (certificates.cert_chain) and one for connections on the local area network (certificates.http_client_ca_certs). If this field is not configured, the platform trust store is used to validate all HTTPS connections. |
EDGA-2854 | Add validation criteria to Edge-to_Edge HTTP Client Connections Certificate Fingerprint Validation has been added to the EMS and LSR. The feature allows you to restrict HTTPS communication on the local area network to a set of known trusted endpoints, and provides an additional layer of validation beyond server certificate validation. |
EDGA-2915 | Support Host Name Validation for Platform WebSocket Connections Support has been added for TLS host name validation for WeSsocket connections to the ThingWorx Platform. This feature is enabled by default, but can be disabled for testing purposes using the new disable_hostname_validation option in config.json.. For more information, refer to TLS Host Name Validation. |
Issues Fixed | |
EDGA-2796 (15146278) | DNS Rebinding Attack The EMS provides additional checks when processing HTTP requests to ensure the host header sent in the request matches the host used by the server. |
EDGA-2824 (15225766) | Running the GetLogData service on an EMSGateway Thing in Composer causes EMS to crash This issue is fixed in this release. |
EMS and LSR, Version 5.4.7 (C SDK 2.2.6)
The 5.4.7 release of the EMS is built on release 2.2.6 of the ThingWorx Edge C SDK, which means that it includes the following changes that affect the EMS:
• Upgrade of OpenSSL libraries to v.1.1.1c.
• For CSDK-1720, SFID C15034738, a fix for an issue that caused file transfers to the ThingWorx Platform to fail if the file was between 8114 and 8118 bytes long.
 | OpenSSL v.1.1.1c implements TLS v.1.3, and you can use it between the EMS and an LSR device. Once the ThingWorx Platform is updated to support TLS v.1.3, you will be able to use it between the EMS and the platform. |
The following table lists and briefly describes the changes in this release of the EMS and LSR:
ID (SFID) | Description |
|---|---|
Enhancement | |
EDGA-2452 | Upgrade OpenSSL to v.1.1.1c. The EMS now provides the OpenSSL 1.1.1c libraries on all supported processors and operating systems. In addition, the non-FIPS OpenSSL 1.0.2 libraries have been removed. Finally, the OpenSSL 1.0.2L FIPS libraries have also been removed. This release of the EMS does not support FIPS. |
Issues Fixed in This Release | |
EDGA-2431 | When EMS is run as a service on Linux, the log can fail to be written to the publish directory. This issue is fixed in this release. The log is written as expected. |
EDGA-2433 (14931683) | EMS tunnel unable to set certificate chain, client certificate, and key file. When using a client certificate, a certificate chain, and key files, the EMS cannot make a remote VNC connection to an edge device. This issue is fixed in this release. |
EDGA-2410 | Updates to the EMS GetLogData() service. Fixed issues preventing the GetLogData() service from working with the updated EMS log format, which was introduced in a previous EMS release. This update allows the GetLogData() service to be used on the EMS to pull data from the EMS log over REST, as described in the topic, GetLogData, in the Help Center for the EMS and LSR. |
EDGA-2486 | Removed idle_timeout and other tunnel configuration options from config examples. Removed several deprecated tunnel configuration options from EMS configuration file examples. idle_timeout, read_timeout, chunk_size, and max_concurrent have been removed as they are no longer set from the Edge but can be set from the ThingWorx Platform in the StartTunnel services request. |
EMS Version 5.4.6 (C SDK 2.2.2)
The 5.4.6 release of the EMS is built on release 2.2.2 of the ThingWorx Edge C SDK, which means that it includes the security changes in that release of the C SDK. See the C SDK release notes for details about the changes in v.2.2.2. The following table describes the changes in this release of the WS EMS.
ID (SFID) | Description |
|---|---|
EDGA-2283 (14803827,14593755) and EDGA-2267 | Upgrade OpenSSL to version 1.0.2r for EMS. This release of the EMS is built using the C SDK v.2.2.2. The AxTLS library has been removed from the EMS distribution bundle and the OpenSSL, v.1.0.2r libraries are provided in the EMS distribution bundle. The documentation for the WS EMS has been updated to reflect these changes. |
EDGA-2275 | Documentation updates for EMS v.5.4.6. The ThingWorx Edge MicroServer Developer’s Guide, v.5.4.6, has been updated for the changes in this release. In addition, the EMS has its own help center on the PTC Support site, at https://support.ptc.com/help/thingworx/edge_microserver/en/. This help center has all the content of the Developer's Guide. |
EDGA-2244 | NTLM proxy support found not working in EMS 5.4.0 This issue is fixed in this release. |
EDGA-1097 | Lua Script Resource cannot connect to an HTTP server listening on a port > 32767. This issue is fixed in this release. |
EMS Version 5.4.5 (C SDK 2.2.0)
The 5.4.5 release of the EMS is built on release 2.2.0.of the ThingWorx Edge C SDK, which means that it includes all the changes made for releases 2.1.5 and 2.2.0 of the C SDK. Refer to the C SDK release notes for information about the changes in the 2.2.0 and 2.1.5 releases. The following table describes the enhancements and the issues fixed in this release of the EMS:
ID (SFID) | Description |
|---|---|
Enhancements | |
EDGA-1478 | A new configuration option has been added to config.json, config.complete, and config.documented to allow you to specify what cipher suites are used by the edge device when communicating with the ThingWorx Platform. It supports the OpenSSL Cipher List format, as described here: https://www.openssl.org/docs/man1.0.2/apps/ciphers.html This option is only supported on EMS releases that use OpenSSL; axTLS releases ignore this option. |
EDGA-1765 | A new configuration option, ws_connection.compression, allows you to enable or disable websocket compression. This option is available in the config.json, config.complete, and config.documented files of the EMS. Previously, websocket compression was always enabled. |
EDGA-1848 (14231681) | Updates have been made to the ws_connection default settings in config.json.complete and config.json.documented to better match settings used by the ThingWorx Edge C SDK. For example, the message_idle_time is now set to a default value of 50 seconds. |
Issues Fixed in This Release | |
EDGA-1778 (14211095) | When running the EMS as a service, it was possible for the EMS to become stuck in a state where it would not shut down properly when a 'stop service' request was made, requiring it to be killed. This issue has been fixed in this release. |
EDGA-1836 | If the EMS was run as a service and was able to connect but not successfully authenticate with ThingWorx within 60 seconds, it would 'hang' and not try to reconnect. This issue is fixed in this release. |
EDGA-1854 | This issue has been resolved as part of PTC’s continued investment in helping customers reduce risks associated with security threats. |
EDGA-1855 (PSPT-5919) | The default certificate and private key have been removed from the EMS. This means that you must configure the HTTP Server of the EMS to use your own certificate and private key when running with SSL/TLS. |
EMS Version 5.4.4 (C SDK 2.1.4)
The 5.4.4 release of the EMS is built on release 2.1.4 of the ThingWorx Edge C SDK, which includes all the changes made for release 2.1.3 of the C SDK. Refer to the C SDK release notes for information about the changes in the 2.1.3 and 2.1.4 releases. The following table describes the issue fixed in this release:
ID (SFID) | Description |
|---|---|
EDGA-1784 | This fix resolves an edge case that could occur during file transfers when websocket compression was in use and could cause the file transfer to fail. |
EMS Version 5.4.3 (C SDK 2.1.2)
The 5.4.3 release of the EMS is built on release 2.1.2 of the ThingWorx Edge C SDK. Refer to the C SDK release notes for information about the changes in that release. The following table lists the enhancement provided in this release:
ID (SFID) | Description |
|---|---|
Enhancement | |
EDGA-1471 | Rebuild Duty Cycle in the EMS With this release, the behavior of EMS for the duty cycle feature has changed to enable it to track file transfers and tunnels, as well as property and service requests from the ThingWorx Platform. Duty cycle will not disconnect the EMS from the platform if any of the following conditions are true: • A message has been received from the platform during the last delay_duty_cycle time interval. • A message has been sent to the platform but no response has been received yet. • A file transfer is pending or in progress. • A remote session (tunnel) is in progress (open). Finally the EMS will not be disconnected from the ThingWorx Platform immediately after starting up. Instead, the EMS will disconnect at the next Duty Cycle event after startup. For more details, refer to the section on configuring duty cycle modulation in the ThingWorx Edge MicroServer Developer’s Guide, v.5.4.3 or later, or visit the ThingWorx Edge MicroServer (EMS) Help Center . |
EMS Version 5.4.2 (C SDK 2.1.2)
The 5.4.2 release of the EMS is built on release 2.1.2 of the ThingWorx Edge C SDK. Refer to the C SDK release notes for information about the changes in that release. The following table lists the issues fixed in this release:
ID (SFID) | Description |
|---|---|
EDGA-1613 | Changes have been made to how the Lua Script Resource’s /script and /scriptcontrol REST endpoints work out-of-the-box. By default, you will not be able to use these endpoints to dynamically create, update, delete, or restart scripts using the REST API. Any requests to these services will result in a 405 – Method Not Allowed error. This feature can be enabled by adding the line scripts.script_resource_enable_rest_services = true to your config.lua |
EDGA-1598 | Move LSR index page off of / and into help.html For this release, the current index page contents for the LSR help has been moved to a help page. You can reach the help page at /help.html, /help, or /help/. The new index page is completely blank. |
EDGA-1594 (14175756) | Add note in EMS/LSR documentation that usernames should not contain a ":" (colon) character. For this release, a new topic has been added to the EMS guide and the Help Center that addresses this issue, in the context of using REST APIs with EMS and LSR. Refer to the developer’s guide included in your distribution bundle or the ThingWorx Edge MicroServer (EMS) Help Center. The topic title is "Running REST API Calls with Postman on EMS and LSR. |
EDGA-1593 | EMS TRACE logs Basic Auth header. EMS was adding the value of the Authorization header on TRACE level. With this release, all Authorization headers are obfuscated in the logs. |
EDGA-1566 (14167223) | Add CSRF token support to the REST API in the EMS and LSR. This change now requires any requests from a client that can change state (such as POST, PUT or DELETE) include a CSRF token in the headers of their request. This token will be provided by the server and put into response header with the key x-csrf-token. The client must include this same header and token value with any request that can change state. The token will change periodically based on the csrf_token_rotation_period value set in config.json/config.lua. The default period is every 10 minutes. Neither the EMS nor the LSR require changes or configuration updates to support CSRF tokens. The tokens are enabled by default. Applications that use the REST interface of the EMS or LSR will need to be updated to include the CSRF token, or CSRF protection must be disabled (not recommended). You can disable CSRF protection by adding the line enable_csrf_token = false in the http_server struct of config.json (EMS) or scripts.script_resource_enable_csrf_token = false` in config.lua (LSR). CSRF protection is enabled only when authorization is enabled as well. If authorization is disabled, no token values will be used. PTC recommends always using TLS, enabling authorization, and encrypting sensitive credentials in configuration files. |
EMS Version 5.4.1 (C SDK 2.1.2)
The 5.4.1 release of the EMS is built on release 2.1.2 of the ThingWorx Edge C SDK. Refer to the C SDK release notes for information about the changes in that release. The following table lists the issues fixed in this release:
ID (SFID) | Description |
|---|---|
Enhancements | |
EDGA-1409 | EMS REST API service TestPort does not work as described. CAUSE: The TestPort service was expecting a full infotable representation rather than the simplified infotable representation. RESOLUTION: The TestPort service now supports simplified infotables. In addition support for additional optional parameters has been expanded. For example: { "host": "127.0.0.1", // Required "port": "80", // Required "useSSL":false, // Optional "useProxy": false // Optional } |
EDGA-1406 | Update the topic for the Restart service. For any edge-side restart requests to work correctly, the Restart REST service relies on a previously undocumented configuration parameter (restart) to be set in the config.json file of the EMS. Information about this configuration option has been added to the developer’s guide for the EMS and to the ThingWorx Edge MicroServer (EMS) and Lua Script Resource Help Center. In the left navigation panel of the help center, go to > > . |
EDGA-1102 | Update Developer's Guide to include all LSR security-related options. A new group of topics, called “Configuring a Lua Script Resource”, has been added to developer’s guide included in your distribution bundle and to the ThingWorx Edge MicroServer (EMS) Help Center The security-related topics in this section are “Configuring the Connection from the LSR to the EMS” and “Configuring the HTTP Server for the LSR (SSL/TLS Certificate)”. |
Issues Fixed in This Release | |
EDGA-1543 (14154298) | The rap_password does not work using AES. CAUSE: An entry in config.lua did not accept an encrypted password. All other entries did/do accept the encrypted password. This release resolves this issue. |
EDGA-1473 | Update note about kEDH ciphers in EMS developer's guide. RESOLUTION: The note about cipher suites in the EMS Developer's Guide has been changed for this release to say the following: If your application communicates with an instance of the ThingWorx Platform that uses Java 1.7, the cipher suite list should include !kEDH (as shown below) to disable ephemeral Diffie-Hellman ciphers . Otherwise, ephemeral Diffie-Hellman (EDH) key exchange will fail, and your EMS will be unable to connect to the platform. <CipherSuites>DEFAULT:!kEDH</CipherSuites> |
EDGA-1470 (C14006638) | "TW_VALIDATE_CERT: Certificate rejected" is output on Start Tunnel with a Remote Access Widget, even though ThingWorx successfully connected with EDGE MicroServer 5.4.0 This issue is fixed in this release. |
EDGA-1469 | EMS doesn't set tunnel TLS configuration settings unless a proxy is used. CAUSE: The initialization code of the EMS configured TLS settings on the tunnel Manager only if a proxy was set. RESOLUTION: The proxy check has been removed so that the tunnel settings are configured, regardless of a proxy being set. |
EDGA-1465 Ubuntu 16.04 SF ID 14067293 Ubuntu 12.04.5 SF ID 14129246 | Lua Script Resource appears to hang on Linux operating systems when trying to communicate with the EMS without TLS. RESOLUTION: The EMS and LSR can now communicate with each other, and things running the LSR show up as bound in ThingWorx Composer when the HTTP server of the EMS is not using SSL (ssl = false) and the LSR is not using SSL to communicate with the EMS (rap_ssl = false). |
EDGA-1454 | EMS HTTP Server logs IP addresses in network byte order. CAUSE: The HTTP Server of the EMS was writing IP addresses to the log in reverse order because IP addresses were stored internally in network byte order rather than host byte order. This issue is fixed in this release. |
EDGA-1414 (14043263) | Configuring SSL/TLS certificates validation is inconsistent in ThingWorx Edge Microserver 5.4. In previous release of the EMS the cert_chain parameter expected an array value. This changed in 5.4.0 and cert_chain now expects a string that points to a single file that contains all Certificate Authority (CA) certificates used for validation. This change was not reflected throughout the Developer's Guide. RESOLUTION: cert_chain is now defined correctly as a string (cert_chain : "/path/to/ca_root.pem", ) throughout the Developer's Guide.. |
EDGA-1408 | EMS returning '402' instead of '403' for Forbidden errors. This issue is fixed in this release. |
EDGA-1105 | EMS causing SSL_READ errors to appear in the logs of the LSR when SSL is used.. This issue is fixed in this release. |
EMS Version 5.4.6 (C SDK 2.2.2)
The 5.4.6 release of the EMS is built on release 2.2.2 of the ThingWorx Edge C SDK, which means that it includes the security changes in that release of the C SDK. Refer to the C SDK release notes for details about the changes in v.2.2.2. The following table describes the changes in this release of the EMS.
ID (SFID) | Description |
|---|---|
EDGA-2283 (14803827, 14593755) and EDGA-2267 | Upgrade OpenSSL to version 1.0.2r for EMS This release of the EMS is built using C SDK v.2.2.2. The AxTLS library has been removed from the EMS and the OpenSSL, v.1.0.2r libraries are provided in the EMS distribution bundle. The documentation for the EMS has been updated to reflect these changes. |
EDGA-2275 | Documentation updates for EMS v.5.4.6. The ThingWorx Edge MicroServer Developer’s Guide, v.5.4.6, has been updated for the changes in this release. In addition, the EMS has its own help center on the PTC Support site, available from the ThingWorx Help Centers page on the PTC Support site. For information about v.5.4.5 and earlier, refer to the EMS section of the original help center in the ThingWorx Edge SDKs and ThingWorx Edge MicroServer Help Center. |
EDGA-2244 | NTLM proxy support found not working in EMS 5.4.0 This issue is fixed in this release. |
EDGA-1097 | Lua Script Resource cannot connect to an HTTP server listening on a port > 32767. This issue is fixed in this release. Refer to CSDK-1576 in the v.2.2.2 release notes of the C SDK. |
EMS Version 5.3.4 (C SDK 1.5.1 and 1.5.2)
The EMS v.5.3.4 is built on C SDK v.1.5.2, which includes changes for C SDK v.1.5.1. Refer to the C SDK release notes for information about those releases.
ID / SFID | Description | ||
|---|---|---|---|
Enhancements | |||
EDGA-1035 | Limitations on log files have been added to the logging persistence function. The total log size on disk will not exceed the configured value. A new property, buffer_size, allows you to specify the maximum size of a single log message (in bytes). In addition, the property, flush_chunk_size, has been added to allow you to the number of bytes to write before flushing to disk. These properties are available in the config.json.complete configuration file in the EMS installation. | ||
EDGA-1034 | The same format is now used in log messages written to the console as in log messages written to the persisted log files. The log messages are no longer wrapped in a JSON object. The persisted log files are just text files. Their content will match what is printed out on the console. | ||
EDGA-1031 | Enforce a Sleep inside the Software Update State Machine. Certain states do not have anything that enforces an idle timeout AND they can spin a tight loop that can consume the CPU at 100 percent. RESOLUTION: After analyzing each state as to whether a sleep needs to be added in the "main campaign execution loop", a sleep has been added to the START_DOWNLOAD state. While in this state, the addition of the sleep prevents the possibility of a state sitting in a tight loop and consuming all of the CPU. Note that sleeps already did and still do exist in the DOWNLOADING, WAIT_FOR_DOWNLOAD, WAIT_FOR_INSTALL states. A sleep is not needed for the ABORTED, FAILED, DOWNLOADED, INSTALLING, NOTIFIED, and CREATED states. | ||
EDGA-909 | The timestamps for log messages on EMS now show the actual time rather than the time that the log messages were written to the stream in the logger thread. This change applies to both EMS and the Lua Script Resource (LSR). | ||
Issue Fixed in This Release | |||
EDGA-1050 / 13318364 | Asset Deployments Failing, Requiring LSR Restart When an asset deployment fails as a result of EMS disconnecting and reconnecting during a download, any subsequent deployments to that asset fail until the Lua Script Resource (LSR) is restarted. | ||
Special Note | |||
| |||
EMS Version 5.3.3 (C SDK 1.5.0, which includes C SDK 1.4.0 & 1.4.1)
ID / SFID | Description |
|---|---|
Enhancement | |
EDGA-811 | Add new configuration option to config.json (tick_resolution). The documentation for EMS has been updated for the change in the C SDK (CSDK-862) that has been merged into EMS for this release. |
Issues Fixed in This Release | |
EDGA-829 13609759 | Stopping the EMS overwrites any changes in the config.json file. This issue is fixed in this release. |
EDGA_818 13603198 | The new FIPS EMS v5.3.2.1693 crashes when first connecting, even if the specified port is wrong. This issue is fixed in this release by the merge with C SDK 1.4.1. |
EDGA-735 13318364 | LSR can hit 50% CPU when waiting for file transfers to finish Package deployments in ThingWorx Utilities SCM failed because the file did not fully transfer to the edge device. When this happens, the LSR hit the CPU at 50%. This issue is fixed in this release. |
EDGA-682 13414038 | LSR pushes null property (with Value 0) to platform when property retrieval fails Properties are initialized with the value 0. When the getProperties service and subsequent handler read call are made, they return a 500 error response. However, the start script does not check the response and just sets the property as if the value has changed. The LSR is setting properties to 0, as they are initialized with that value, every time they cannot be retrieved. Error handling has been added to the code that verifies the response type from getProperties. The change has been added to template.lua. |
EDGA-648 13394597, 13420582 | luaScriptResources stop working with error message “bad argument #1 to ‘pairs’ (table expected, not nil)” This issue is fixed in this release. |
EDGA-600 | Default values for auto_bind host and port not being used when running in non-gateway mode. the Windows 7 example for EMS 5.3.2 failed with the error emsRequestHandler: Thing not bound to EMS or host is not set. The example is fixed in this release. The code that works is: "auto_bind" [ {"name": "TestRemoteThing", "host": "localhost", "port": 8001, "gateway": false} ] The host and port must be specified when using auto_bind. |
EDGA-581 | Remove MODBUS scripts from EMS distribution. The etc/thingworx/scripts, etc/thingworx/lua and etc/custom/templates directories of the EMS distribution no longer include MODBUS files and pre-compiled Lua binaries. The documentation for the EMS has been updated with these changes for this release. |
EDGA-560 13271857 | Tunnel max_concurrent setting does NOT limit concurrent VNC access to the EMS. The following settings for tunneling are not supported by the EMS: max_concurrent, buffer_size, read_timeout, and idle_timeout are not supported by EMS. The documentation has been updated to remove buffer_size, read_timeout, and idle_timeout. |
EDGA-227 | Specifying an incorrect path in the virtual directory configuration of EMS can cause a core dump This issue is fixed in this release. |
EDGA-218 | EMS not reporting duty cycle. With the duty cycle set to 50%, the EMS connects to ThingWorx server properly, but the generated Thing object does not show up as disconnected or disappear at any time. There are no log messages to indicate that the EMS went offline. This issue is fixed in this release. |
EMS Version 5.3.2.1693 — Issues Fixed (C SDK 1.3.5)
ID / SFID | Description | ||
|---|---|---|---|
EDGA-567 | Attempting to run the install.bat file in order to run EMS and Lua Script Resource as services was failing on the sc create lines. Instead of creating a service, the help message for the command was displayed. This issue is fixed in this release. | ||
EDGA-546 / C12947309 | EMS could not reconnect to ThingWorx server via a proxy server. This issue was fixed by changes in the C SDK 1.3.5. | ||
EDGA-141 | When all the parameters of config.json were not contained within curly brackets ({}), the EMS would report an error, overwrite the existing config.json file, and exit. This issue is fixed in this release. | ||
EDGA-78 | The EMS distribution bundle now includes doc directory that contains the PDF of the ThingWorx Edge MicroServer (EMS) Developer’s Guide for this release and a /doc directory that contains the luadoc files. In addition, the doc/index.htm file has been removed. | ||
Known Issue | |||
EDGE-1964 / CSDK-14 | The Edge device (EMS) cannot establish a secure websocket connection (WSS, SSL) to a ThingWorx server. The error appears as Error 0, Error initializing SSL connection, twWs_Connect: Error restarting socket. Error 0, and/or No compatible ciphers when an EMS device attempts to connect. This issue applies to the C SDK 1.3.2 through 1.3.5; the .NET SDK 5.6.2, through 5.6.4, the EMS 5.3.2.x, and the iOS SDK 1.0. CAUSE: Versions of Apache Tomcat 8.0.35 and above have disabled RSA-based ciphers by default due to forward secrecy concerns. Refer to https://tomcat.apache.org/tomcat-8.0-doc/changelog.html for 8.0.34.). The axTLS libraries used by the EMS (and all ThingWorx C SDK, .NET SDK, and iOS SDK) support two encryption ciphers: TLS_RSA_WITH_AES_256_CBC_SHA and TLS_RSA_WITH_AES_128_CBC_SHA. Any application that uses SSL for Edge connections if the Tomcat server is upgraded to 8.0.35 or later may be affected by this change to Tomcat. WORKAROUNDS: • Downgrade to a version of Tomcat version 8.0.33 or lower. • In the server.xml configuration file of Tomcat, explicitly define a list of ciphers that includes the axTLS ciphers. For an example with a list of ciphers supported in Tomcat version 8.0.36, refer to https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS245522.
| ||
This release includes fixes that were made for the C SDK, versions 1.3.3, 1.3.4, and 1.3.5. | |||
EMS Version 5.3.2 — Enhancements and Issues Fixed (C SDK 1.3.2)
ID | Description | ||
|---|---|---|---|
Enhancements | |||
EDGE-975 | UpdateSubscribedPropertyValues is now always triggered after property updates. | ||
EDGE-239 | A section on using FIPS has been added to the user guide for EMS. This documentation also includes information from the fix for EDGE-1250 (enabling client authentication). | ||
EDGA-80 | This release includes a subdirectory, doc, that contains the *.luadoc files that provide details for the LuaScriptResource. | ||
EDGA-78 | The EMS distributions now include the following items: • A doc directory that contains the user’s guide. • A subdirectory, doc/lua, that contains the microserver/doc/*.luadoc files. In addition, the distributions no longer contain a file called version.txt. | ||
EDGA-72 | connect_retries is missing from config.json.complete. This property has been added to config.json.complete for this release. | ||
Issues Fixed | |||
EDGE-1485 | The FIPS build of the EMS for this release enables you to set up a secure connection to the ThingWorx Platform on Windows 7 machines. | ||
EDGE-1250 | Client authentication cannot be enabled for the C SDK. The C SDK uses the axTLS library for authentication. axTLS does NOT support client authentication. However, the EMS provides a build that contains OpenSSL and FIPS (select the bundle that has “FIPS” in its name). Use this build when client authentication and FIPS mode are required. Refer to the section on FIPS in the PDF that accompanies the EMS bundle. | ||
EDGE-1076 | The following timeouts are now documented in config.json.complete and can be read from config.json by the EMS: • socket_read_timeout • frame_read_timeout • ssl_read_timeout | ||
EDGE-874 | The EMS was responding very slowly to requests, in comparison to v.5.2.2 and 5.3.0. This issue is fixed in this release. | ||
EDGE-758 | When calling the GetRemoteMetadata service from the ThingWorx Platform via a Connection Server (v.6.5.11, 7.0, and 7.0.1), the Connection Server logs an error and the ThingWorx Platform service times out. The EMS is successfully receiving the request and sending packets back to the Connection Server. This issue is fixed in this release. | ||
EDGA-346 | Memory leak while decoding JSON into InfoTable under certain conditions. This issue is fixed in this release. | ||
EDGA-345 | Investigate memory leaks in EMS This issue is fixed in this release. | ||
EDGA-344 | PUT request caused memory leak in EMS. This issue is fixed in this release. | ||
EDGA-226 | FIPS EMS Crashes. This issue is fixed in this release. | ||
EDGA-217 | EMS Memory Leaks and Crashes on Linux. This issue is fixed in this release. | ||
EDGA-211 | The wsems -version command now returns the correct version. | ||
EDGA-178 | The EMS now passes proxy configuration settings to the Tunnel Manager so that in a network that is set up to route all traffic through a proxy, the tunnel requests are no longer blocked. | ||
EDGA-123 | When you start EMS without a config.json file, error messages explaining what has happened now appear. The EMS will try to load an existing .booted configuration file when the config.json is missing. When it fails to find a .booted file, it goes back to the original. When that fails again, the EMS will tell you that it failed to load any configuration file. In addition, if the config.json file is not formatted correctly, the EMS will report an appropriate error message. | ||
Known Issue | |||
EDGE-1964 / CSDK-14 | The Edge device (EMS) cannot establish a secure Websocket connection (WSS, SSL) to a ThingWorx server. The error appears as Error 0, Error initializing SSL connection, twWs_Connect: Error restarting socket. Error 0, and/or No compatible ciphers when an EMS device attempts to connect. This issue applies the C SDK 1.3.2, .NET SDK 5.6.2 and 5.6.3, EMS 5.3.2, and iOS SDK 1.1. CAUSE: Versions of Apache Tomcat 8.0.35 and above have disabled RSA-based ciphers by default due to forward secrecy concerns. See https://tomcat.apache.org/tomcat-8.0-doc/changelog.html for 8.0.34. The axTLS libraries used by the EMS (and all ThingWorx C SDK, .NET SDK, and iOS SDK) support two encryption ciphers: TLS_RSA_WITH_AES_256_CBC_SHA and TLS_RSA_WITH_AES_128_CBC_SHA. Any application that uses SSL for Edge connections if the Tomcat server is upgraded to 8.0.35 or later may be affected by this change to Tomcat. WORKAROUNDS: • Downgrade to a version of Tomcat version 8.0.33 or lower. • In the server.xml configuration file of Tomcat, explicitly define a list of ciphers that includes the axTLS ciphers. For an example with a list of ciphers supported in Tomcat version 8.0.36, refer to https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS245522.
| ||
This release also includes fixes/improvements that were made for the C SDK 1.3.2. | |||
EMS Version 5.3.1 — Enhancements and Issues Fixed (C SDK 1.3.1)
ID | Description |
|---|---|
Enhancements | |
EDGE-953 | The tw_dir.pwd() function has been added to the Lua Script Resource for this release. |
EDGE-890 | The config.json.complete file has been updated to reflect recent changes. In particular, you can no longer specify an array of ThingWorx Platform addresses for the connection from EMS to the ThingWorx Platform. You can only specify ONE destination host and port. If you have Microservers that have this configuration, note that this version of EMS does not error when it encounters the array. It tries the first address and, if that fails, it returns an error to that effect. |
EDGE-831 | Add inputs to install scripts for the EMS that allow renaming of the services. The inputs already existed in the Windows install script and are now documented. The inputs for Linux scripts have been added and are documented in the ThingWorx Edge MicroServer Developer’s Guide (PDF) that accompanies the EMS distribution. |
EDGE-821 | The ThingWorx Edge MicroServer Developer’s Guide (PDF) now provides the versions of the libraries required for use on supported Linux platforms. |
EDGE-837 | The API documentation (luadoc) for Lua has been added to the EMS distribution bundle. |
EDGE-706 | The ThingWorx Edge MicroServer Developer’s Guide (PDF) has been extensively revised for this release. In addition, it now documents the REST API supported by the EMS. |
EDGE-363 | The install scripts for the EMS on Linux have been enhanced to support other platforms. |
Issues Fixed | |
EDGE-829 | The ListFiles service gives different result for EMS 5.3 and 5.0. The ListFiles service in this release (5.3.1) now returns the path without the file name, as it did in release 5.0. |
EDGE-823/EDGE-499Case 12819599 | The EMS running as a service on a Netbiter ec350 device failed to start up and displayed the following message: Error creating BSD socket. This release resolves this issue. |
EDGE-818 | EMS crashes (SIGABRT) during LSR startup on some Linux platforms. This problem occurs only on Linux systems with libc.so.6-2.6 or older, which are not supported. Refer to the revised ThingWorx Edge MicroServer Developer’s Guide that accompanies this release for information about the C libraries that are required. The new section with this information is in Chapter 2 and is called “Libraries”. |
EDGE-803 | Cannot POST events through EMS REST interface. This release resolves this issue. |
EDGE-762 | Updating multiple properties using REST API call vian EMS error. This issue has been resolved. Refer to Tech Support Article 000225416. |
EDGE-756 | EMS does not connect with offline storage. This release resolves this issue. |
EDGE-752 | The PUTJson service strips the URI query parameter. This release resolves this issue. |
EDGE-680 | Offline storage stores data when turned off in the configuration file. This release resolves this issue. |
EDGE-605 | EMS cannot save the config.json.booted file when the -cfg flag is used. This release resolves this issue. |
This release also includes fixes/improvements that were made for the C SDK 1.3.1. | |
EMS Version 5.3.0 (C SDK 1.3.0)
New Features and Fixes |
|---|
• The Content Loader services have been modified. In earlier releases, services were too strict when they interpreted the content-type of response headers. • EMS now handles requests made by the Content Loader services for any bound Thing. • The script resource no longer prepends the * character to the p_data file of an Identifier. • Duplicate entries in GetDirectoryStructure have been removed. • Various memory leaks have been fixed. • The distribution bundle of this release includes an updated version of the document, WebSocket Edge MicroServer (EMS) User’s Guide. • This release also includes fixes/improvements that were made for the C SDK 1.3.0. |
EMS Version 5.2.2 (C SDK 1.3.0)
New Features |
|---|
• This release contains an updated Lua script to facilitate the functionality that updates software, which is part of the ThingWorx Converge RSM application. |
EMS Version 5.2.0 (C SDK 1.3.0)
New Features |
|---|
• The EMS now uses the C SDK for its WebSocket library. • This release also includes fixes/improvements that were made for the C SDK 1.3.0. |
Bug Fixes |
• The HTTP server now uses the SDK twSocket, even in non-SSL mode. • For the HTTP server, you can now configure the timeout setting for reading content. • The issue with AxTlsStream in the Linux version of the HTTP server is fixed. • The script, modbus.lua, has been updated with fixes from the Technical Sales department. • A deadlock that was caused by the request to unbind in certain situations has been fixed. • The bug in the EMS handler that removes resources has been fixed. • LSR (Lua Script Resource) scripts can now exit out of a tw_utils.psleep() call when a script is shut down. • The staging directory of EMS can now reference a virtual directory (virtual_dir) or a directory on the file system. • Fix for EDGE-256: The LSR now includes the correct information about data shapes when browsing the properties in an infotable. • Fix for EDGE-186: An asterisk (*) is no longer prepended to the Identifier; the EMS now connects on second startup. • The default size of the buffer of TlsStream has been changed to 16K. • The console is now more responsive. • An issue wherein the EMS would shut down while it tried to connect has been fixed. • Fix for EDGE-303: The software update now works in Lua with 5.0. • Support for OpenSSL FIPS support has been added for Win32 platforms. • A bug that caused large multipart messages to fail has been fixed. |
EMS Version 5.1.0.8
New Features |
|---|
• The EMS now supports transfers of files whose name or path contain multi-byte characters. This feature includes virtual directories that are configured at the server. |
Bug Fixes |
• The handling of incoming messages that occurs within the sendMessageBlocking function has been fixed so that the function handles responses only. This fix avoids deadlocks in certain situations. • The twMessage_Send function has been changed to verify that the EMS is authenticated before it sends. • The code that sends offline messages to insert a new RequestId has been changed in order to remove any potential conflicts from a previous ID. • Mutex protection has been added in the twTlsClient_Reconnect and twTlsClient_ConnectSession functions. • A segment fault that occurs while the EMS stores non-persistent, offline messages has been fixed. • The copyright for documentation has been updated. • The Location property is now registered so that it shows up when browsed. |
EMS Version 5.0.4.121
New Features |
|---|
This release includes changes to the way that EMS validates SSL certificates. The default behavior has been changed so that EMS does NOT accept self-signed certificates, and always validates the SSL certificate provided by the ThingWorx server. This change can result in the following errors at startup: • If you are currently connecting to a ThingWorx Platform that uses a self-signed certificate, you must explicitly enable the acceptance of self-signed certificates in your EMS configuration. • If you are currently connecting to a ThingWorx Platform that uses a certificate that has been signed by a trusted certificate authority (CA), you must obtain the root certificate of that CA, in .pem format. You must then deploy that root certificate with your EMS. Alternatively, you can disable certificate validation (NOT recommended, especially in a production environment). You can change the following configuration options in the 'certificates' section of in your config.json file: "certificates" : { "validate": true | false, // Enable/disable certificate validation "cert_chain": [ "/path/to/ca_root.pem" ], // Inform EMS about CA root cert "allow_self_signed": true | false // Accept self signed cert from server } Note on signed certificates: Certificates in the certificate chain of the server must be signed, using one of the following signing algorithms: SHA1, MD 5, or MD2. |