> 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/uso-generico-de-onesait-ecosystems-editran-ff.md). # Generic use of Onesait Ecosystems ยท Editran/FF In general, the complete process of using the Editran/FF application could follow the following steps: * The starting situation is to have configured, from the interface *AdminFF,* a signing application with certain local users at one end and a verification application, with the same name and the same users as the signing application, but of remote type, at the other end. * The interface *UserFF* will offer each local user the files that, according to the configuration made, they can view and sign. When users access each file and sign it, a new file is created in the signatures directory with the same name as the signed one but with the extension .*p7b* or .*xsig.* * According to the defined configuration, when all the files in the application have the required signatures, a user will enable the sending of the application. This process generates a new signature file whose content is the list of application files and the DNs of the certificates of the users who have signed each of them. The enabling of sending can also be done forcibly, that is, even if signatures are missing, provided that this permission has been granted to some of the users in the configuration. * Sending the contents of the signature or data directories from the sending end to the receiving end. * At the receiving end, the reception is validated (a receipt acceptance file is generated). * Sending the receipt acceptance file to the sending end. * Validation at the sending end of the Sending-Receiving (a file with this information is generated). Next, each of the tasks listed in these seven steps will be described in detail. --- # 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/uso-generico-de-onesait-ecosystems-editran-ff.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.