F7 Trading System
12 Mar 2024

Decommissioning of deprecated self-signed client certificates (API, GUI) for Eurex Repo F7 – IMPORTANT, action required!

As previously announced (Technical Information eMail, Feb-26 and Jan-15, 2024) Eurex Repo F7 Simulation will stop accepting old self-signed client certificates for API and GUI from the upcoming weekend (March 16th) onwards.

The timeline for all is F7 environments is as follows:

  • March, 16th, 2024
    Eurex Repo F7 Simulation will no longer accept self-signed client certificates for incoming Repo F7 API or Repo F7 GUI connections
  • April, 27th, 2024
    Eurex Repo F7 Production will no longer accept self-signed client certificates for incoming Repo F7 API or Repo F7 GUI connections
  • May, 11th, 2024                 
    Eurex Repo F7 Advanced Simulation will no longer accept self-signed client certificates for incoming Repo F7 API or Repo F7 GUI connections

All customers are required to switch to the new DBAG signed client certificates on or prior to the dates listed above. Usage of the deprecated self-signed client certificates will no longer be possible after the announced dates.

Please see chapter 6 of the document “F7 Connectivity Guide” for a full description of the new DBAG signed client certificate workflow.

The document can be downloaded from the Connectivity Overview page on Eurex.com and from the DBAG Repo Member Section via following this path: Resources > Eurex Repo > System Documentation > Access and Certificates

Support contact: Customer Technical Support: +49 (0) 69 2 11-1 08 88 / cts@deutsche-boerse.com

Market Status

XEUR

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message. 

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.

An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.