> 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/aplicaciones-para-verificar-firmas.md). # Applications for verifying signatures The configuration of the applications for verifying signatures must be agreed with the originating end of those signatures. Specifically, both ends will agree on the signature format, the number of required signatures, the certificates with which they can be created, and the signing rules that must be met for the files to be considered correctly and sufficiently signed. To configure an application whose purpose is to verify signatures, click the button ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/UaDMX2wLhsEHCuWYtfIQ/image1.png) . In the view that will be displayed, click the icon ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/vWAylqInfg0h302VhPP9/image2.png) to add a new application for verification, in which the following parameters must be filled in: ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/U8jw4T7tGquoJZgyCYSF/image3.png) * **Name**: identifier of the application in the system. **The words *****apps***** and *****users***** are reserved and cannot be used to identify applications.** * **Signature mode**: drop-down list in which the signature format used in the signature files to be received and validated will be selected. **For applications related to Iberpay, XADES\_DETACHED\_INTERNA\_EXPLICITA\_UNFICH must be chosen.** * **Signature directory**: path where the signature files to be validated will be located. The directory must exist. * **Data directory**: path where, during the verification process, the data file contained in the signature file will be extracted in the signature modes in which it is included: XADES\_DETACHED\_INTERNO\_IMPLICITO, XADES\_DETACHED\_INTERNO\_EXPLÍCITO\_UN\_FICH, XADES\_ENVELOPED, XADES\_ENVELOPING\_IMPLICITO and PKCS7\_ATTACHED. In the remaining modes, it will be the path where the data file will be located, a file that will have been received together with the signature file, but separately from it. The directory must exist. * **XAdES policy**: this is the XML file that contains the set of conditions and characteristics that signature files must include in order to be considered valid. It will only be configured if the signing end has used EPES security level (for example, by using one of the templates included in the Editran/FF installation that have “EPES” as part of their name). **For applications with Iberpay, it must remain blank.** * **Check revocation**: parameter indicating whether or not the revocation status of each certificate found in the signature files being validated should be validated. For this functionality, the machine must have internet access; the proxy section must be configured if applicable or the parameters for connection with remote Editran OCSP must be specified, both in the general configuration of Administrator/FF. * **Associated with tx**: parameter indicating that the application is intended to be associated with Editran. In this version this functionality is not operational, so it must remain unchecked. * **Rules:** button from which to access the view to define the validation rules for the corresponding application. For more detail, see the section **3.5.1.** ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/wAp0gQKEgtW3pDhcFWce/image4.png) To delete an application, select it in the list and click the button ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/aFHJ4rty238u6Haiqoen/image5.png) . --- # 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/aplicaciones-para-verificar-firmas.md?ask=&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.