> 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/definition-of-own-rsa-and-remote-rsa-profiles-in-100099940.md). # Definition of own RSA and remote RSA profiles in 100099940 The administrator of entity 100099940 (Pepe Pérez González) creates subsystem ‘1’ OWN RSA, option 6.2. If a subsystem already existed, he could use it to export and send the keys that subsystem had to entity 200099940, but let us suppose that entity 100099940 is starting with key management. When creating it, you can change the labels, but it is not recommended. Note that, when creating this record, it does not indicate anywhere that the keys it will include are for entity 200099940. ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 15:57:45 OWN RSA KEY MANAGEMENT | |-----------------------------------------------------------------------------| | | | SUBSYSTEM.....: 1 LOCAL ENVIRONMENT..: 100099940 | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: LOCAL | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | | | PAIR LABEL: LABEL.PRODUCTS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVATE | | KEY GENERATION LENGTH: 2048 (1024/2048/4096) | | | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` Next, generate the key pair in the same option 6.2. This causes the procedure indicated in the environment profile, ZTBGP1GC, to be launched, which generates the private-public RSA key pair with Version 01, and in that record, once the procedure ends, the following appears on that screen: ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 15:57:45 OWN RSA KEY MANAGEMENT | |-----------------------------------------------------------------------------| | | | SUBSYSTEM.....: 1 LOCAL ENVIRONMENT..: 100099940 | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: LOCAL | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | | | PAIR LABEL: LABEL.PRODUCTS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVATE | | KEY GENERATION LENGTH: 2048 (1024/2048/4096) | | | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 01 20160609-162740 20160609-162740 4-ACTIVE (S)ELECT. VIEW PUBLIC | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` Next, since this is the first time it will exchange keys with entity 2000999940, it enters option 6.3 and creates the RSA own-keys record, subsystem 1, local 100099940, remote 200099940 Note: In the RSA subsystem for Signing, nothing is indicated, since this is the first key exchange with that remote. ``` ------------------------------------------------------------------------------- | 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.PRODUCTS.EDI.100099940.1.000000000.RSA.LOCAL.PRIVATE | | 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 | | ---- --------------- --------------- ----------- --- | | 10 20160609-162740 20161019-164235 1-GENERATED (S)ELECT.VIEW PUB.LOC. | | | | | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` Note that the labels do not include the remote code, because they will be the keys exported from option 6.2 (they have not yet been exported). Once this is done, the administrator of entity 100099940 creates the foreign subsystem (as indicated by the administrator of entity 200099940). This subsystem is created in option 6.4. ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:01:34 FOREIGN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 2 LOCAL......: 100099940 REMOTE.....: 200099940 | | | | SUBSYSTEM DESCRIPTION..........: SECONDARY RSA SUBS. | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTS.EDI.100099940.2.200099940.RSA.FOREIGN.PUBLIC | | 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 | | ---- --------------- --------------- ----------- --- | | | | | | | | | | | | EXIT, EXIT | ``` Note that, in this case, the remote code does appear in the labels Note: In the RSA Signing subsystem, nothing is indicated, since this is the first key exchange with that remote. At this point, the administrator of 100099940 is ready to receive the key from 200099940 Now we enter the definition of the own RSA and remote RSA profile on the other end, 200099940. The administrator of entity 200099940 has already worked with key management and already had own subsystem 2 created (option 6.2), so it does not need to be created. At this moment in that option it has: ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:04:14 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 2 LOCAL......: 200099940 REMOTE.....: 100099940 | | | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTS.EDI.200099940.2.000000000.RSA.LOCAL.PRIVATE | | ACTIVE KEY LENGTH IN THE SUBSYSTEM...: | | | | RSA SIGNING SUBSYSTEM...: 0 | | RELATIONSHIP OF PRIVATE AND PUBLIC KEYS (LABEL + VERSION) | | VERS GEN. DATE-TIME MODIF. DATE-TIME STATE SEL | | ---- --------------- --------------- ----------- --- | | 01 20050830-105719 20160511-133714 4-ACTIVE (S)ELECT.VIEW PUB.LOC. | | 02 20080704-122959 20130211-142214 4-ACTIVE (S)ELECT.VIEW PUB.LOC. | | | | | | | | EXIT, VIEW PUBLIC KEY | ------------------------------------------------------------------------------- ``` Specifically, it already has 2 keys defined in that subsystem, V1 and V2, which it exported to other remotes, so it is going to export V3 to remote 100099940. Next, since this is the first time it will exchange keys with entity 1000999940, it enters option 6.3 and creates the RSA own-keys record, subsystem 2, local 200099940, remote 100099940 Note: In the RSA subsystem for Signing, nothing is indicated, since this is the first key exchange with that remote. ``` ------------------------------------------------------------------------------- | 14/02/2011 EXCHANGE KEY MANAGEMENT EDITRAN 5.3 | | 16:58:47 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 2 LOCAL......: 200099940 REMOTE.....: 100099940 | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTS.EDI.200099940.2.000000000.RSA.LOCAL.PRIVATE | | 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 | | ---- --------------- --------------- ----------- --- | | | | | | | | | | | | EXIT, CREATE | ------------------------------------------------------------------------------- ``` Note that the labels do not include the remote code, because they will be the keys exported from option 6.2 (they have not yet been exported). Once this is done, the administrator of entity 200099940 creates the foreign subsystem (as indicated by the administrator of entity 100099940). This subsystem is created in option 6.4. ``` ------------------------------------------------------------------------------- | 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.PRODUCTS.EDI.200099940.1.100099940.RSA.FOREIGN.PUBLIC | | 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 | | ---- --------------- --------------- ----------- --- | | | | | | | | | | | | EXIT, EXIT | ``` Note that, in this case, the remote code does appear in the labels Note: In the RSA Signing subsystem, nothing is indicated, since this is the first key exchange with that remote. At this point, the administrator of 100099940 is ready to receive the key from 200099940, but since they agreed that the administrator of 200099940 would send first, Luis enters option 6.3 again, key generation and export, so that it ends up as follows: ``` ------------------------------------------------------------------------------- | 23/05/2017 KEY EXCHANGE MANAGEMENT EDITRAN 5.3 | | 16:00:28 OWN RSA KEYS ASSOCIATION | |-----------------------------------------------------------------------------| | SUBSYSTEM.: 2 LOCAL......: 200099940 REMOTE.....: 100099940 | | | | SUBSYSTEM DESCRIPTION..........: SUBS.PRINCIPAL RSA | | ADMINISTRATOR NAME...........: REMOTE | | ADMINISTRATOR PHONE.........: | | EDITRAN/P SERVICE APPLICATION...: TELEGC | | PAIR LABEL: LABEL.PRODUCTS.EDI.200099940.2.000000000.RSA.LOCAL.PRIVATE | | 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 | | ---- --------------- --------------- ----------- --- | | 10 20160609-162740 20161019-164235 1-GENERATED (S)ELECT.VIEW PUB.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/definition-of-own-rsa-and-remote-rsa-profiles-in-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.