> 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-iseries-en/editran-ff/configuration-of-editran-xades/configuration-of-certificates-to-be-signed/storage-of-aliases-and-passwords.md).

# Storage of aliases and passwords

Since the signatures will be performed unattended, it is necessary to carry out a prior configuration in which the full path of each certificate to be used for signing, its alias (whose method of retrieval has been described in the previous section), and its corresponding password are associated. To perform this configuration, run gestor\_claves.sh in the SignatureServices/bin directory and follow these steps: a. Use option "2) Save a key". The options available are: 1) List keys, 2) Save a key, and 3) Delete a key. b. Keystore path. Enter the full path of the certificate to be installed (usually with .pfx or .p12 extension), where the signer's key pair is stored. c. Keystore password: Enter the certificate password. d. Alias: Enter the alias obtained in the previous section. The script does not check whether the certificate exists, whether it contains that alias, or whether the password is correct; if any data is incorrect, the signing process will fail. The associations made are stored securely, encrypted under AES. This configuration is saved in the FicheroKeyStores.txt file in the conf directory. The script lists the paths of the .pfx or .p12 certificates and their aliases. For example: KeyStore / XAdES /rsc/keystore/Ciudadano\_autenticacion\_activo.pfx; Alias: autenticacionactivo![](https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=-1355392697/https%3A%2F%2Ffiles.gitbook.com%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F80nfuaOloGPZthms7LSJ%252Fuploads%252Fgit-blob-781c1e753c6c05cd0a36ecfba7347d6c034100a6%252Fimage%2520\(117\).png%3Falt%3Dmedia)![](https://images.gitbook.com/__img/dpr=2,width=760,onerror=redirect,format=auto,signature=1056380089/https%3A%2F%2Ffiles.gitbook.com%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F80nfuaOloGPZthms7LSJ%252Fuploads%252Fgit-blob-02846dad0497006d2ccb9001d45361288ee45790%252Fimage%2520\(118\).png%3Falt%3Dmedia)


---

# 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-iseries-en/editran-ff/configuration-of-editran-xades/configuration-of-certificates-to-be-signed/storage-of-aliases-and-passwords.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.