> 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-v6.2-windows-en/comandos/enviardn.md).

# SendDN

Utility to facilitate the administration of the profiles to the *Editran/FF Administrator* with regard to the certificates with which users will sign the files. When run, the following window appears:

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/UzS1FPlTYXYdJY55qJVj/image1.png)

By pressing the different buttons *OWN, THIRD-PARTY, INTERMEDIATE AUTHORITIES, ROOT AUTHORITIES* and *OTHERS* *OWN STORES* the certificates of the corresponding type that are installed on the computer will be displayed.

Only the certificates of *OWN* that include a private key will be suitable for signing. The button *View* *certificate*, can be used to view the selected certificate and check whether it includes a private key; only then will it be valid for signing. Likewise, selecting the “Certification path” tab in that same dialog will verify that the status of all certificates in the certification path is valid; otherwise, they must be installed properly.

![](https://content.gitbook.com/content/AKp9o4ESamTHpX42EKdv/blobs/AqQCBqiojuV8aHDkyzxZ/image2.png)

Once the check has been made, those certificates from said store that the user wants to use with Editran/FF will be selected; there can be up to three. Certificates showing problems in the Error column such as “Expired certificate”, “Revoked certificate”, “Certificate about to expire”, etc. should not be selected.

The buttons *Copy to Clipboard, Generate file* and *Send email* collect the information that the Editran/FF configuration profiles need to know about each of them; they are: subject DN, issuer DN and *serial number.* The information is saved in a specific format that allows it to be incorporated into *AdminFF*. Once the information has been obtained, whichever button is used (email or file), it will be sent to the server so that, once there, it can be incorporated into the profiles from the user's configuration window (buttons “*Clipboard”* or “*File”*), see **4.2.1.**

Alternatively to using this tool and also on the workstation where the certificates are installed, from a web browser or by running Windows certmgr.msc, each certificate can be exported to format .*cer* (export without the private key; it is the appropriate format when the certificate is to be outside the owner's reach). Once the .*cer*, they will be sent to the server and the necessary data for the profiles will be incorporated again with **4.2.1**, button “*File”.*


---

# 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-v6.2-windows-en/comandos/enviardn.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.