> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/publico-editranff-lite-v7-open-en/windows/instalacion/configuracion-de-signatureservices/configuracion-de-certificados/certificados-de-firmantes-remotos.md).

# Remote signers' certificates

When EditranFF is used to verify received signatures, it will be necessary to have information about the certificates that the sending end of those signatures is going to use, in order to include it in the configuration.

In EditranFF, the information about the certificates whose signatures are to be received and verified can be specified either with the .cer file (recommended option) or with its DN (this option will be discontinued in later versions). Whichever system is chosen by the receiving end, the sending end of the signatures must send it the public part of all the certificates it is going to use to carry them out.

Then, only if the receiving end wants to carry out the configuration based on the DNs (not recommended option), it must obtain said data through the batch obten\_dn.bat located in the SignatureServices/bin directory of the installation. The following steps will be carried out:

**a**. Choose the option **"2) Public key certificates".**

**b**. Enter the full path of the certificate from which you want to obtain the data (.cer extension).

**c**. Optionally, define the directory where the file with the data will be saved.

**d**. The DN and the rest of the certificate information will be displayed on screen.

In the section **3.3** it explains in detail how to include the information of the remote certificates in the configuration, either by .cer or by its DN.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.editran.onesait.com/documentacion-editran/publico-editranff-lite-v7-open-en/windows/instalacion/configuracion-de-signatureservices/configuracion-de-certificados/certificados-de-firmantes-remotos.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.