A sign-on service for terminals is generally made up of two parts:
Sign-on service | |
Part 1 | Part 2 |
The service asks the user for identification, reads the authorization data with MGET, and transfers this data to openUTM for checking. The service is not yet assigned to any user ID. | openUTM has accepted the authorization data and has assigned the sign-on service to the established user ID. |
openUTM may insert an intermediate dialog between the first and second parts of the signon process if the period of validity of the password has already expired and the application has been generated with grace sign-on. A K message informs the user that the password is no longer valid. At the same time, the user is prompted to enter the previous password and a new password.
Special cases of the sign-on service for terminals
The sign-on service must be changed accordingly for the UTM generation of LTERM partners with automatic KDCSIGN.
LTERM partners with automatic KDCSIGN
The sign-on service receives the information that the user ID is already known to the system when calling SIGN ST. An intermediate dialog can now be run to change a password whose period of validity has expired.