Information for TSOs and users

Application downloads

Please follow the links to get on the right download page

Download ECP Endpoint

Download EDX Toolbox

ECCo SP - Fall Release 2023

We are excited to announce the availability of the Fall release 2023, packed with new features, enhancements, bug fixes, technological advancements, and security upgrades. You can now access the release through your usual channels for ECP and EDX. In the ECCo SP Fall Release, you’ll find ECP version 4.12.0 and EDX version 1.13.0. Both versions are offered as complete installations or upgrades.

This release encompasses a wide range of improvements, including the following notable features:

  • Improve Health Actuator functionality.
  • Display of warning message (to restart Brokers) on Component Directory after network certificates import.
  • Automatic restart of ECP CD after certificate renewal.
  • Informing ECP EP about the revocation in CD.
  • ECP/EDX Logging improvement.
  • Maintaining Message Path Consistency.

ECCo SP Alert: Vulnerability in ActiveMQ

A critical vulnerability, identified as CVE-2023-46604 in ActiveMQ, has been reported through Apache CVE Publication.

Impact on ECCo SP:

This vulnerability specifically impacts the OpenWire protocol, whereas ECCo SP employs the AMPQS protocol by default. To ascertain which protocol is in use, please refer to the <transportConnectors> section in the activemq.xml file, applicable to both the internal broker and ECP Broker. By default, if “name” is set to “amqp+ssl” in the transportConnector element, it signifies the utilization of the AMPQS protocol. In case the OpenWire protocol was in use, “name” would be set to “default” or “auto” or “openwire”.

Furthermore, an examination of the ActiveMQ fix’s source code changes (accessible at https://issues.apache.org/jira/browse/AMQ-9370) has been conducted to identify the affected classes. A corrective method was introduced in the BaseDataStreamMarshaller.createThrowable methods for all OpenWire versions. We conducted debugging on ECCo SP, employing breakpoints within these methods, and observed that these methods were never invoked.

In conclusion, ECCo SP remains unaffected by this vulnerability, unless it is configured to use the OpenWire protocol, which has never been supported by ECCo SP or mentioned in the ECCo SP documentation.

Attention Users: Important Message About Changes

Keycloak Integration

ECCoSP currently utilizes Spring Boot 2.7, which is scheduled to reach its End of Life on November 18, 2023. Consequently, an essential upgrade to Spring Boot 3.0 is imperative. However, this upgrade is presently blocked by third-party dependencies, most notably, Keycloak.

The issue lies in the fact that these dependencies must migrate from the old ‘javax’ namespace to the new ‘jakarta’ namespace. While Keycloak introduced support for the ‘jakarta’ namespace in its 22nd release, this update was not incorporated into the deprecated Keycloak Spring Boot adapter and will not be done in the future as well.

Given these circumstances, the CDS WG has made a decision to remove the KeycloakWebSecurityConfigurerAdapter class and all associated Keycloak properties starting from the ECCo SP Spring 2024 Release and onwards. Consequently, users who rely on Keycloak for authentication will need to make a transition to LDAP authentication or can integrate Keycloak with LDAP authentication as a viable alternative. A comprehensive guide for integrating Keycloak with LDAP will be included as part of the package.

Removal of Windows Installers for Central Components

To reduce complexity and based on the assumption that all projects are already utilizing Linux machines for central components, we will remove the Windows installers for the Component Directory and Broker starting from the ECCo SP Spring 2024 Release and continuing into the future.

Windows Server 2016

In our Fall 2024 Release, we intend to phase out support for Windows Server 2016 while simultaneously introducing support for Windows Server 2022.

Docker Images access

ECP and EDX components can be run within Docker containers.

Option 1: Docker Hub Access

The ECP and EDX components can be seamlessly executed within Docker containers, facilitated through Docker images conveniently hosted on the ENTSO-E Docker hub.

To initiate the process, simply pull the required Docker images from the ENTSO-E Docker hub. These pre-packaged images are readily available, ensuring a smooth deployment experience.

For additional details or assistance, please feel free to reach out to ecp@entsoe.eu . They can provide you with the necessary access to the Docker images on the Docker hub.

Option 2: Direct Download from Website

You can download the ECP Endpoint and EDX Toolbox Docker binaries directly from our official website. To begin the download process, simply click on the link located at the top of this page. This action will redirect you to the designated download page.

NOTE: - To access the Docker test environment, Docker Compose YAML file, and Helm charts, please download the installation package from our website. After downloading, navigate to the specified location: ECP-4.XX.0\ECP-4.XX.0.XX-Client\ECP Other Deliverables.

Please refer to the following video for more information:

How to use Docker for ECCo SP

Sandbox Environment

NOTICE - On March 31, 2024, we will be decommissioning the current Sandbox environment. We are actively working on a new setup. While we cannot provide a specific date at this time but we will provide further instructions and details about the new environment once it’s ready for use.

ECCoSP Sandbox environment has been created to provide an easy way to try out the ECCoSP platform. You can explore ECCoSP features in the sandbox and get a first-hand experience of its capabilities. With the ECCoSP Sandbox, you can experiment with the different features and even try out the latest features without having to commit to a full deployment (you still need to install an ECP Endpoint). It can also be used to perform a basic set of smoke tests before installing/upgrading to a new release on your network. So, start exploring and have fun with the ECCoSP Sandbox!

 Please contact ecp@entsoe.eu for further information and access to the sandbox environment.

Projects running ECP & EDX

Many Transmission System Operators (TSOs) rely on ECCoSP as the standard for managing messages exchanged between TSOs and market participants. Moreover, a range of projects utilizing ECP and EDX as a pan-European exchange layer. Notable examples encompass the Transparency Platform, Common Grid Model, OPC/STA, and European balancing platforms such as TERRE, MARI, and PICASSO.

GET THE MOST POWERFUL NEWSLETTER IN BRUSSELS