> 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/clienteff/modos-de-uso-para-firmar-ficheros/firma-con-aplicacion.md).

# Signing with an application

The following will be written:

```
clienteff -firma -aplicacionff [application name] [-fichero [file name]] [-
alias [aliases of the signers, separated by ',']
```

Where:

* **-aplicacionff \[application name]:** name of the signing application configured through AdministradorFF.
* **\[-fichero \[file name]]:** if you want to sign a single file or a limited set of files, include this parameter. Only the file name is needed, not the full path, but it must be in the application's data directory. The metacharacters ‘\*’ and ‘?’ are supported to refer to a set of files.
* **\[-alias \[aliases of the signers, separated by ‘,’]]:** if you want a specific set of users to sign, include this parameter. The users must be linked to the specific application. If the user has an assigned countersigner, the corresponding countersignature will also be performed.

The signed files will be saved in the application's signatures directory.

For example, to sign all files associated with the application *nominas* with all users associated with it:

```
clienteff –firma –aplicacionff nominas
```

To sign the files with the extension *.xml* associated with the application *nominas* with all users associated with it:

```
clienteff –firma –aplicacionff nominas –fichero *.xml
```

To sign all files associated with the application *nominas* with the user *usuario1*, associated with that application:

```
clienteff –firma –aplicacionff nominas –alias usuario1
```


---

# 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/clienteff/modos-de-uso-para-firmar-ficheros/firma-con-aplicacion.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.