> 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/linux/administradorff/firmantes-remotos-o-certificados-cuyas-firmas-se-van-a-recibir-y-verificar.md).

# Remote signers (or certificates whose signatures will be received and verified)

The button will be clicked ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/Xy9kv52H5MzAvYnciJQn/image1.png) to access the view through which the information related to the users or certificates whose signatures are to be received and validated can be configured. In the view, click on ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/Yz1Q6R2t83aLFVQoB4W9/image2.png) to add a new remote user.

![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/WMZQ9nXuzaop5ehzXV5A/image3.png)

As seen in **2.3.3.2**, the certificates whose signatures are received and verified can be provided in two ways: through the .cer file (public part of the certificate and which does not include the private key) or through the certificate DN. The icon ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/e4Lo17TPP4qAxCVMhyiH/image4.png) allows you to select the chosen system to provide that data and will list the signers or certificates configured in one way or the other.

1. Information through CER file (.cer extension). The following data must be completed:
   * **Name**: alias or identifier of the certificate in the system.
   * **Certificate**: path to the public certificate of the signer that the sending side of the signatures will previously have sent to the verifying side. The button ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/1SbuibtRT5fEdL5fRLbk/image5.png) allows the certificate to be located on the machine.

Once the information has been saved, the icon ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/z1eaeaUGZ9Yyyj10g6Hc/image6.png) can be used to view the main data of the public certificate.

![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/CReMSvJzSOoWTnh6hIJa/image7.png)

**This is the recommended system for providing the public certificates of remote signers in the product configuration.**

2. Information through the certificate DN. The following data must be completed:
   * **Name**: alias or identifier of the certificate in the system.
   * **DN**: data from the signer's public certificate that either the sending side or the receiving side will have obtained from the certificate (usually using obten\_dn.sh, which is found in SignatureServices/bin).

**The configuration of information related to the public certificates of remote signers through their DN will be discontinued soon, so its use is not recommended.**

![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/KgnvgDdLeVQ299fiGtAH/image8.png)

To delete a remote user, select it in the list and press the button ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/k0n2wJqmvlRJ4LR38r9Q/image9.png) .

By pressing the button *Save all* ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/FWFAVddxL3I5kZdT97dy/image10.png) at the top, the information will be stored in the system. If there is any problem, an informational message with the cause will appear.


---

# 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/linux/administradorff/firmantes-remotos-o-certificados-cuyas-firmas-se-van-a-recibir-y-verificar.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.