Sign-on process without user IDs

openUTM does not perform a sign-on check for UTM applications for which no user IDs are generated. The clients are signed on under their LTERM names or association names. UPIC clients, HTTP clients  and OpenCPIC clients are not permitted to transfer real user IDs in this case.

If the UTM application uses sign-on services ("Sign-on process with sign-on services"), an application-specific sign-on check can then be performed, e.g. using a database with authorization data.

If sign-on services are not used, the user can work with this application as soon as a connection has been successfully established to the UTM application. In the case of terminals and TS applications (clients with partner type APPLI or SOCKET that communicate via the UTM Socket Protocol (USP) in case of partner type SOCKET), the user receives a message from openUTM depending on whether an open service is still known for this LTERM partner.

• If no open service is known for the LTERM partner in the application, openUTM outputs the UTM message

  K001 Connected to application example - input please

  The user can then start services and enter UTM user commands.

• If an open service is known for this LTERM partner in the application, the output from the last synchronization point of the interrupted service is displayed on the screen and the user can continue the service. See also “Service restart” and “Screen restart” in the openUTM manual „Programming Applications with KDCS”. One of the prerequisites here is that RESTART=YES was generated for this LTERM partner. However, this also means that the user may also be able to continue the service of another user.

Note that openUTM links a service to the LTERM partner in an application without user IDs. An interrupted service can therefore only be continued from the same client, unless the assignment of LTERM partner and physical client (defined in the PTERM statement) is changed accordingly with the administration command KDCSWTCH.

If clients are locked, the behavior is the same as for user IDs; see "Behavior in the event of locked clients/LTERM partners".

CAUTION!

In a UTM application without user IDs, all users have administration authorization.