> 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/ibm-editran-v5.3-comun-z-os-en/editran-ff-instalacion-firma-y-verificacion-v7.1.1/instalacion-de-certificados-en-modo-fichero/fichero-keystore.md).

# Keystore file

The keystore file is a file that contains one or more certificates that will be used for signing. The certificates are obtained by the application user and should be stored in a USS folder or included in one or more keystores whose path we must configure for each Editran/FF user (see [FirmaElectronica-IMS\_v7.0.-IMS](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/IBM/5.3/zOS/editran-ff-instalacion-firma-y-verificacion-v7.1.1/instalacion-de-certificados-en-modo-fichero/broken-reference/README.md) and [Electronic Signature Installation and User Manual-CICS\_v7.0](https://gitlab.devops.onesait.com/onesait/disruptors/ecosystems-editran/editran-documentation/-/blob/public/IBM/5.3/zOS/editran-ff-instalacion-firma-y-verificacion-v7.1.1/instalacion-de-certificados-en-modo-fichero/broken-reference/README.md)) or, if there is a single one, in the default path (by running configuración\_xades.sh, located in the bin directory).

To configure this type of stores, you must run the batch file gestor\_claves.sh, located in the bin directory. This configuration is saved in the FicheroKeyStores.txt file in the conf directory (/u/edisign/conf/FicheroKeyStores.txt).

When the program is run, if the file already exists, it shows us the values we already have saved. Otherwise they will be blank:

```
Current mode: FILE
Saved keys:
KeyStore: rsc/keystore/keyStore.pfx; Alias: XAdES test certificate
1) List the keys
2) Save a key
3) Delete a key
Option (E to exit):
```

The options we have are to list the saved keys, save a new key, and delete an existing key. The data to save for each signer are:

* Keystore path: Path to the keystore where the signer's key pair is stored.
* Keystore password: Password for the keystore.
* Alias: Alias of the key pair we want to use for signing.
* Key password: Password for the key. It can be the same as the keystore password; in that case, leave it blank.

To be able to test the product without needing your own certificates, the keyStore.pfx file that is in the rsc/keystore directory is also included with a test certificate (in the example: /u/edisign /rsc/keystore/keystore.pfx); the alias of the stored certificate is “XAdES test certificate” (password: “password”).

This keystore is already configured in the FicheroKeyStores.txt file and is the one used as the default keystore file in the initial configuration.

If we are in RACF mode, when running the program it will show us a message indicating that no management needs to be done in this regard:

```
Currently in RACF mode, no key management is necessary.
You will exit the application
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/editran-ff-instalacion-firma-y-verificacion-v7.1.1/instalacion-de-certificados-en-modo-fichero/fichero-keystore.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.