PC Configuration
Configuration for communication with CS OTE
Access to the production and test environment of CS OTE
| Description | Production environment | Test environment (Sandbox) |
|---|---|---|
| 1. In the attached file, see the browser configuration process, Mozilla Firefox, Google Chrome and Microsoft Edge with a hardware certificate stored on a USB iKeyToken from the OTECA certification authority. | PC configuration | |
|
Client station configuration for production valid from 26.5.2018 Client station configuration for Sandbox valid from 28.3.2018 |
||
Communication methods with CS OTE
A. through a web browser
B. through a secure email
C. through automatic communication
| Description | Common for Production and Test environment |
|---|---|
|
Signing OTE PKI component for 64bit latest version 2.12 |
|
|
Signing OTE PKI component for 32bit for legacy usage Notice: this version is no longer actively maintained or updated. It is recommended to use the 64-bit version of OTE PKI Client instead. |
|
| Software License Agreement by signing OTE PKI components - Czech only | License Agreement |
| Software License Agreement software application OTE LauncherManager and OTECOM | License Agreement |
If you have been instructed to update PKI component to latest version, you can check currently installed version in:
Start - add or remove programs - find OtePkiClient and see version there.
| Description | Production environment | Test environment (Sandbox) |
|---|---|---|
|
1. This certificate is used for S/MIME message encrypting sent by a participant to the production environment address - csote@csote.ote-cr.cz or the test environment address - cds@cds.sand.ote-cr.cz. A user adds the certificate to the contact - CS OTE recipient. |
This certificate is valid from 20 May 2026 This certificate is valid until 06 June 2026 |
This certificate is valid from 20 May 2026 This certificate is valid until 06 June 2026 |
|
2. Email clients settings manual for sending/receiving encrypted messages to/from CS OTE: MS Outlook 2016 |
||
| Description | Production environment | Test environment (Sandbox) |
|---|---|---|
| 1. Attached form for Automatic communication settings (SOAP communication). | ||
|
2. SSL certificate of the communication server (Let’s Encrypt), which is used for SSL/TLS encryption when your system (application) acts as a client of web services. The renewal of these certificates is performed automatically, and for this reason we recommend validating communication against the Let's Encrypt certificate authority chain. |
|
|
|
Root certificate authorities for the new SSL certificate of the communication server (Let’s Encrypt) |
Let’s Encrypt root certificates | |
|
3. This certificate is used for electronic signature of messages and data sent from CS OTE to the participant. Installation is not required unless special settings of your software for processing are required. This certificate is used for GOs, billing documents and invoices. |
||
|
4. This certificate is used for secure web services (BinarySecurityToken for WS-Security) and for authentication TLS from CS OTE to a participant. |
This certificate is valid until 23 May 2029. |
This certificate is valid until 06 June 2026. This certificate is valid until 04 June 2026, 15:00. |
| Manual for using the certificate in automatic communication (server-server communication and client-server communication) and e-mail communication. |
Using of automatic communication.docx Updated 12 May 2022 |
|
| Description | Electronic seal for download (valid now) | Electronic seal for download (!validity date will be announced!) |
|---|---|---|
|
CS OTE |
This certificate is valid until 04.09.2026 |
CS OTE |
|
Emission Allowances |
This certificate is valid until 04.09.2026 |
Emission Allowances |
|
Guarantees of Origin Register |
This certificate is valid until 04.09.2026 |
EZP |
|
Invoicing |
This certificate is valid until 06.09.2026 |
Invoicing |
|
Sandbox |
This certificate is valid until 04.09.2026 |
Sandbox |
All messages and documents issued by OTE that are currently electronically sealed are sealed using qualified certificates for electronic seals pursuant to Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions and Act No. 297/2016 Coll., on trust services for electronic transactions.
nd confidence-building services for electronic transactions and Act No. 297/2016 Coll. on trust-building services for electronic transactions.
