> 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/electronic-signature/graphical-interface/local-and-remote-users.md). # Local and remote users Users responsible for signing the files to be sent (LOCAL) or verifying the signature of received files (REMOTE). This screen is accessed with option 2.2 of the Editran/FF menu. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/FF ADMINISTRATOR | | 18:57:44 LOCAL AND REMOTE USERS | ----------------------------------------------------------------------------- | | | | | | | | | A ---> ADD | | | | B ---> DELETE | | | | M ---> MODIFICATION (USER REC. AND IN ALL SESSIONS) | | | | C ---> QUERY | | | | | | OPTION...............: C | | USER TYPE (L/R): L (L)OC,(R)EM,( )BOTH | | ENTITY CODE ......: 0 0009999 0 | | USER ALIAS.......: (SPECIF.-STRING) | | | | | ------------------------------------------------------------------------------- ``` We must enter * **Option** * **User type** (local, for our own users, or remote for users of other entities), * **Entity code** to which the user belongs (local Editran code for local users and the remote entity code for remote users), * **Name or alias** with which we will internally identify the user. The user name allows any character, uppercase and lowercase, or spaces. If the user is local, the entity code indicated is the local Editran code. If there are several local codes, sub-environments, different users can be created for each of the sub-environments. A local user can only be used in Editran transmissions for that local code. The aliases of local users can be repeated in other local codes and are considered different users. If the user is remote, the entity code corresponds to the remote code of the Editran session. The aliases of remote users can be repeated in other entity codes. The user cannot be deleted if it is associated with any of the existing rules. Likewise, modifying the user is propagated to all the rules in which it appears. ## Local user Users for signature in sending. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/FF ADMINISTRATOR | | 18:58:06 LOCAL USER | ----------------------------------------------------------------------------- | USER:CICSSITC F-H:20240617-131017 | | SELECTION CRITERIA: ENTITY CODE...: 0 0009999 0 | | USER TYPE..: LOCAL USER ALIAS.: ANAALVAREZ1 | | ATTENTION. THIS MAP HANDLES UPPERCASE AND LOWERCASE. FILL IN APPROPRIATELY. | | ENTER THE PATH OF THE KEYSTORE THAT CONTAINS THE CERTIFICATE OR RACF USER. | | | | CERTIFICATE ALIAS: | | te-5eb3b3d0-aa9d-4d07-9d4d-22b9069caa6d | | | | KEYSTORE PATH: | | rsc/keystore/AnaAlvarezAntunez_Cert_1.pfx | | | | | | RACF USER: | | KEY RING: | | | | | | | | EXIT, MODIF., VIEW ASSOCIATED RULES | ------------------------------------------------------------------------------- ``` Information: * **CERTIFICATE ALIAS**. Alias used to identify the certificate within the Keystore. * There are two types of certificates to use. * Certificates contained in a keystore * **KEYSTORE PATH:** For certificates contained in a keystore, the path of the keystore will be indicated. The user alias and the path, as well as any associated password, must be registered on the EditranSignatureServices server using the gestor\_claves.sh utility * Certificates contained in RACF. * **RACF USER**: Is the owner of the RACF certificate * **KEY RING**: Is the ring (keyring) in which the RACF certificate is included It is reported that this screen supports uppercase and lowercase If on the user screen we press \, we can consult the Rules to which the user is associated. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/FF ADMINISTRATOR | | 18:58:23 RULES ASSOCIATED WITH THE USER | ----------------------------------------------------------------------------- | USER TYPE.: LOCAL ENTITY CODE.: 0 0009994 0 | | USER ALIAS: ISIIGUANA1 | | SESSION STANDARD COMPANY GROUP SIGN CTF | | -------------------------- ----- ------------ --------------- --- --- | | 000099940-A00099940-NORMA3 S S | | 000099940-A00099940-NORM98 S N | | 000099940-A00099940-NORM99 S N | | 000099940-A00099940-TGSS01 N N | | 000099940-A00099940-TGSS02 N N | | | | | | | | | | | | | | | | | | | | EXIT | ------------------------------------------------------------------------------- ``` The header shows the fields for which the query is performed. * **CGO**: (from header). If the user is local, the user's entity will appear as the local code; if it is remote, it will appear as the remote code. * **USER TYPE**: (from header). Local or remote, of the current user. * **USER ALIAS**: (from header). Current user's name. In the query lines, the following will be displayed * **SESSION**: Session to which the user was associated. * **STANDARD**: Banking standard of the rule in which the user is included. * **COMPANY**: NIF and suffix of the rule in which the user is included. * **GROUP**: Group to which the user belongs, or spaces if the user does not belong to a group. * **SIGN**: The user can sign. * **CTF**: The user can countersign. ## Remote user Users for signature verification on receipt. ``` ----------------------------------------------------------------------------- | 24/06/2026 EDITRAN/FF ADMINISTRATOR | | 18:58:40 REMOTE USER | ----------------------------------------------------------------------------- | USER:CICSSITD F-H:20240408-081021 | | SELECTION CRITERIA: ENTITY CODE...: 0 0009994 0 | | USER TYPE..: REMOTE USER ALIAS.: ANAALVAREZ2 | | ATTENTION. THIS MAP HANDLES UPPERCASE AND LOWERCASE. FILL IN APPROPRIATELY. | | ENTER THE IDENTIFICATION OR PATH OF THE PUBLIC REMOTE CERTIFICATE. | | | | REMOTE CERTIFICATE IDENTIFICATION (D/P): P (DN/PATH) | | DN/PATH: | | AnaAlvarezAntunez_Cert_1.cer | | | | | | | | | | | | | | | | | | | | EXIT, MODIF., VIEW ASSOCIATED RULES | ------------------------------------------------------------------------------- ``` * **REMOTE CERTIFICATE IDENTIFICATION**: Indicates the type of information we are going to enter about the remote user's certificate. You can choose between D (DN) or P (PATH). * **DN**: 'Distinguished name'. It corresponds to the DN included in the digital certificate with which the files will be signed in the remote entity. It is one of the two ways to identify the certificate. If we do not know the DN, we can obtain it from the ZTBFFSAL file * **PATH**: Corresponds to the relative or absolute path where the public digital certificate file is located, with which the files will be signed and which will be provided by the remote entity. --- # 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/electronic-signature/graphical-interface/local-and-remote-users.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.