Contact: Eurex Repo Sales
Importance: High Priority
Summary:
To ensure the highest possible level of security and privacy against eavesdropping, a two-factor authentication is required for every participant. Client certificate authentication is required for both Internet and Leased Line access.
Initially introduced for the F7 FIX Gateway, Repo F7 is now transitioning all API and GUI client certificates from the previously used self-signed client certificates to new client certificates, which can be created in the DBAG Member Section with a simple click and automatically signed by Deutsche Börse's Certificate Authority (CA).
This new workflow is significantly easier and reduces tasks on the client side. Furthermore, the new DBAG CA signed client certificates can be used and can be revoked immediately without any delay for GUI and FIX (client certificates for F7 API still require one end-of-day processing to become active).
Please use the tile labeled "Eurex Repo F7 GUI/API/FIX" under "Requests & Configuration" in the DBAG Member Section to create and manage these new DBAG CA signed client certificates for all types of Eurex Repo F7 access.
Please refer to chapter 6 of the document "F7 Connectivity Guide" for a full detailed description of the new DBAG signed client certificate workflow.
- All customers are advised to switch to the new DBAG signed client certificates as soon as possible.
After moving to new DBAG signed client certificates in Eurex Repo F7 Simulation and Advanced Simulation first, participants should then consider switching their client certificates for Eurex Repo F7 Production.
Existing self-signed certificates can still be used during the transition period. But all newly created client certificates must be created using the new workflow. It is currently planned to decommission all existing self-signed client certificates by the end of Q1/2024.
Support contact: Customer Technical Support: +49 (0) 69 2 11-1 08 88 / cts@deutsche-boerse.com
Best regards,
Your Eurex Repo Team
Repo.Sales@eurex.com
Please note: this is not about the API server/broker certificates which are updated yearly. This change is about the client certificates.
