> 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-cics-en/key-manager/operation-example/rsa-key-issuance-from-entity-100099940.md). # RSA key issuance from entity 100099940 The administrator of entity 100099940 must: * Export the key of its own RSA subsystem 1 * Send it to the remote. To do this, access option 6.3, and export and send, leaving: ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:00:28 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 1 LOCAL......: 100099940 REMOTE.....: 200099940 | | | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTOS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVADA | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: | | | | RSA SUBSYSTEM FOR SIGNING...: | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 01 20160609-162740 20161019-164235 1-GENERATED (S)ELEC.VER PUBL.LOC. | | | | | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` Automatically, a pre-issuance process has been launched that has loaded the V1 key and is sending it to remote 200099940. Once the post-issuance process is launched, the administrator of entity 100099940, in option 6.3 will see ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:00:28 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 1 LOCAL......: 100099940 REMOTE.....: 200099940 | | | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTOS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVADA | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: | | | | RSA SUBSYSTEM FOR SIGNING...: | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 01 20160609-162740 20161019-164235 2-SENT (S)ELEC.VER PUBL.LOC. | | | | | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` In entity 200099940, the administrator, in option 6.4, once the post-reception process has finished will see: ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:01:34 FOREIGN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 1 LOCAL......: 200099940 REMOTE.....: 100099940 | | | | SUBSYSTEM DESCRIPTION..........: SECONDARY RSA SUBS. | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTOS.EDI.200099940.1.100099940.RSA.AJENA.PUBLICA | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: 0 | | | | RSA SUBSYSTEM SIGNED.......: | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 03 20100210-174527 20050210-174527 2-RECEIVED | | | | EXIT, MODIFY | ------------------------------------------------------------------------------- ``` Afterwards, in entity 200099940, a confirmation file has been generated, which begins to be emitted automatically to entity 100099940. Once this transmission ends, and after its post-issuance process, in entity 20099940, the administrator accesses option 6.4 and will find that the key status has changed to ACTIVE. ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:01:34 FOREIGN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 1 LOCAL......: 200099940 REMOTE.....: 100099940 | | | | SUBSYSTEM DESCRIPTION..........: SECONDARY RSA SUBS. | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTOS.EDI.200099940.1.100099940.RSA.AJENA.PUBLICA | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: 0 | | | | RSA SUBSYSTEM SIGNED.......: | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 03 20100210-174527 20050210-174527 4-ACTIVE | | | | EXIT, MODIFY | ------------------------------------------------------------------------------- ``` Once this transmission ends, and after its post-reception process, in entity 100099940, the administrator accesses option 6.3 and will find that the key status has changed to ACTIVE. It must enter through modification and include the RSA subsystem for signing, so that if new keys are issued they will be signed by a previously exchanged key. ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:00:28 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 1 LOCAL......: 100099940 REMOTE.....: 200099940 | | | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTOS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVADA | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: | | | | RSA SUBSYSTEM FOR SIGNING...: 1 | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 01 20160609-162740 20161019-164235 4-ACTIVE (S)ELEC.VER PUBL.LOC. | | | | | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` --- # 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-cics-en/key-manager/operation-example/rsa-key-issuance-from-entity-100099940.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.