> 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/association-of-remote-rsa-keys-administration.md).
# Association of remote RSA keys (administration)
It is accessed with option 3 and displays the following panel:
The meaning of the fields is as follows:
* Option. Mandatory field.
* Subsystem. Accepts values A-Z and 0-9. It is the name of the RSA key subsystem that the remote entity has registered as local and that it will notify us about so that we can register it as remote.
* Local environment. EDITRAN code of the main local environment.
* Remote environment. EDITRAN code of the remote entity.
If a record is selected, the following screen is displayed (some fields may appear differently depending on the access option, registration-deletion, modification, or query):
\\
In the case of query:
Vers Gen. Date-Time Modif. Date-Time Status Sel(PUBLIC KEY)---- -------------------- ------------------- ----------- ---01 20050218-175626 20050220-105545 3 OPERATIONAL02 20050231-154832 20050301-123451 3 OPERATIONAL03 20050131-154832 20050301-123451 4 ACTIVE
In the case of modification:
Vers. Creation Date-Time Modif. Date-Time Status A/C(ACTIVE/CANCEL KEY )---- ----------------- ------------------- ------------ ---01 20050218-175626 20050220-105545 3 OPERATIONAL02 20050231-154832 20050301-123451 3 OPERATIONAL03 20050131-154832 20050301-123451 4 ACTIVE
The requested data are:
* **Remote description**
* **Editran/P application**, through which we will receive the remote's public key.
* **Public label**. Name of the remote public label. The default label is displayed. The administrator is responsible for ensuring that they do not match those of another subsystem, etc.
The default label is:
* **Local-alias.remote-NIF.subsystem.Owner**
* **RSA subsystem for signing.** Protected field, which is filled in with the subsystem chosen by the remote to sign (upon receiving the file with its key).
Next come the **versions** for which a key pair has been generated, and their status (active, cancelled, or operational). Only one can be “active.” When new keys are RECEIVED, they move to received and active status, and if there was an active one, it becomes operational.
In the case of a query, if a version has been selected (S), the public key is displayed in clear text and hexadecimal, with all protected fields (the selected version is included in the label).
\\
---
# 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/association-of-remote-rsa-keys-administration.md?ask=&goal=
```
`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.
.png?alt=media)
.png?alt=media)
.png?alt=media)