> 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/gestor-de-claves/definitions-and-screens/management-of-own-rsa-keys-administration-and-generation.md).

# Management of own RSA keys (administration and generation)

It is accessed with option 2 and displays the following panel (default fields are shown; in the local environment, if there is a license in editran, the general local environment is shown):

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-aca3bbda6e5a5d3987ab75847fe513d9cdb73f8b%2Fimage%20(195).png?alt=media" alt=""><figcaption></figcaption></figure>

The meaning of the fields is as follows:

* **Option**. Mandatory field.
* **Subsystem**. It accepts values A-Z and 0-9. It is the name of the RSA subsystem that we are going to register. For example, we may have test or production subsystems, monthly or annual exchange subsystems, subsystems for one group of entities or another, etc.

If selected, the following map is displayed:

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-6b2fced617285d1ee14e45215be373d100fac576%2Fimage%20(196).png?alt=media" alt=""><figcaption></figcaption></figure>

In the case of query:

<sup>Vers Gen. Date-Time Modif. Date-Time Status Sel(PUBLIC KEY)</sup>

<sup>--— ------------------ ----------------------- ---------- ---</sup>

<sup>01 20050216-175626 20050218-105545 3 OPERATIONAL</sup>

<sup>02 20050217-160044 20050218-130015 4 ACTIVE</sup>

In the case of modification:

<sup>Vers. F-Date-Time Gen. F-Date-Time Modif. Status A (ACTIVE KEY )</sup>

<sup>---- ------------------- ------------------- ------------ ---</sup>

<sup>01 20050216-175626 20050218-105545 3 OPERATIONAL</sup>

<sup>02 20050217-160044 20050218-130015 4 ACTIVE</sup>

As we are in RSA, when registering a subsystem, it will probably serve us for several remote entities.

The requested data are:

**Local description**

**Editran application**, it is still a “template” before defining the remote systems associated with the subsystem.

**Private and public label**. A default label is displayed. The administrator is responsible for them, ensuring they do not match those of another subsystem, etc. They cannot be modified if there are associated remote records or if a key pair has been generated.

The default labels are:

**Local-alias.own-NIF.subsystem.Owner**

Next come **the versions** for which a key pair has been generated, and the state they are in (active or operational). Only one can be “active”. When new keys are generated, they become active and if there was already one active, it becomes operational.

In the case of a query, if a version (S) has been selected, the public key is shown in clear text and hexadecimal (the selected version is included in the label).

In the case of generation, an intermediate confirmation screen is displayed. If they confirm and if there is a cl procedure in the local environment, it is launched:

<figure><img src="https://2621858476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F80nfuaOloGPZthms7LSJ%2Fuploads%2Fgit-blob-8491b5668664426fc0df74707759cfa339f49434%2Fimage%20(200).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/gestor-de-claves/definitions-and-screens/management-of-own-rsa-keys-administration-and-generation.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.
