> 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/configuracion-general.md). # General configuration When the graphical interface of **AdministradorFF**, the General settings are shown selected in the button bar. This view can always be accessed by clicking the button ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/8ySuzkt4xVGEorym90HG/image1.png) on the sidebar. The view is composed of the following parameters: * **Certificate store system (required):** indicates how the certificates to be used for signing are supplied to the application. In FILE mode, the classic method of obtaining certificates from .pfx or .p12 files is used. In HSM mode, the certificates will be contained in a cryptographic card, to which the application will connect via the PKCS#11 standard to obtain the certificates and sign with them. When switching from one mode to another, the application will display a message warning that several configuration values need to be reviewed in order to sign and verify properly. **The product in this version does not include the Windows certificate store and it is not an eligible option.** * **Path to PKCS11 library (required in HSM mode):** The path to the library that allows connection to the HSM via PKCS11. Its name and location vary depending on the HSM used. * **CA truststore (required in FILE mode)**: collects the directory and password of the .pfx file that contains all the CA certificates of the certificates whose signatures will be created or validated. By default, the value indicated in SignatureServices/conf/xades.properties appears, which is the location of the file SignatureServices/rsc/truststore.pfx included with the product. * **CA token (required in HSM mode)**: collects the name of the token that contains all the CA certificates of the certificates whose signatures will be created or validated. * **Connection to remote Editran OCSP (optional)**: this is the machine where the service will be deployed to check the revocation status of the certificates, provided that this check is desired and the UNIX machine where Editran/FF has been installed does not have internet access. * **Proxy (optional)**: collects all the parameters necessary to make internet connections through a proxy. * **Default configuration for signing:** the following set of parameters must necessarily be completed if the sign without application mode is to be used (see section **4.1.1**) and may be omitted otherwise. * **Mode**: the type of signature with which all files are to be signed. * **XAdES template**: XML-formatted document, according to Editran's proprietary schema, which defines sets of features configurable in XAdES signatures (applied hash algorithm length, BES or EPES protection level, mandatory labels, etc.). Examples corresponding to the different signature modes of the combo are provided with the distribution. They can be modified and new ones created, as long as the final template file complies with the SignatureServices/rsc/plantillafirma.xsd schema. **To exchange signed files with Iberpay, the following must be chosen:** **Mode: XADES\_DETACHED\_INTERNAL\_EXPLICIT\_UNFICH** **XAdES template: \[installation path]/SignatureServices/plantillas/pln-di-e-unfich-BES.xml** * **Check revocation status**: parameter used to indicate whether the revocation status of the certificates should be validated each time they are used to sign a file. For this functionality, the machine must have internet access; the proxy section must be configured, if applicable, or the parameters for Connection to remote Editran OCSP must be specified, both in this same view. * **Default keystore (optional)**: allows specifying the certificate store for signing that will be used by default. If signing will be done with more than one signer/certificate, it must be left blank. ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/z883wkVVmkZxI44FGcmR/image2.png) By pressing the button *Save all* ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/BdCRmJVG9GpuW070eOdY/image3.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. ![](https://content.gitbook.com/content/04WMoASrRViaNE1vVCAL/blobs/PZlGMvceCthSQ0ROZWhf/image4.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/configuracion-general.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.