> 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/instalacion/configuracion-de-signatureservices/configuracion-de-certificados/certificados-de-firmantes-locales.md).

# Local signers' certificates

## 2.3.3.1.1 Obtaining a certificate alias

To obtain the aliases of the certificates with which local signatures will be made, the program must be executed **keytool** located in the bin directory of the Java installation. The following call will be made for each certificate to be used:

```
keytool -v -list -storetype PKCS12 -keystore [full path to .p12 file]
```

The command produces output like the one shown below. The Alias Name value will be collected (highlighted in the example):

```
Keystore Type: PKCS12
Keystore Provider: SunJSSE
Your keystore contains 1 entry
Alias Name: le-02818664-5fba-4495-a83c-088014814bff
Creation Date: 06-Sep-2019
Entry Type: PrivateKeyEntry
Certificate Chain Length: 2
[…]
```

## 2.3.3.1.2 Storing the certificate alias and password

Run **gestor\_claves.sh** in the directory **SignatureServices/bin** and carry out the following steps:

**a**. Choose the option **"2) Save a key".**

**b**. Enter the full path of the certificate to be installed (normally it has the .pfx or .p12 extension).

**c**. Enter the certificate password.

**d**. Enter the alias obtained in the section **2.3.3.1.1.**

**The script does not check whether the certificate exists, whether that is its alias, or whether the password is correct. If any of the indicated data is incorrect, the signing process will fail.**

The associations made are stored securely, encrypted under AES.

Once the process is finished, the script will list the paths of the .pfx or .p12 certificates and their aliases already saved. For example:

```
KeyStore: /opt/editranff/SignatureServices/rsc/keystore/usuariof.p12; Alias: le-
02818664-5fba-4495-a83c-088014814bff
```


---

# 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/instalacion/configuracion-de-signatureservices/configuracion-de-certificados/certificados-de-firmantes-locales.md?ask=<question>&goal=<user_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.