Single signon in the roll-and-scroll
environment is only available for Telnet-based sessions.This version of the RPC Broker supports Kernel's single signon from a client workstation to the server. Users need only sign on once (i.e., enter their Access and Verify codes) when accessing both a VISTA roll-and-scroll (e.g., Lab, Pharmacy) and a VISTA client/server GUI-based application (e.g., PCMM, CPRS) on the same workstation, regardless of which application is started first. Once logged into the server, the user will not be asked to re-enter their Access and Verify codes for any subsequent VISTA applications they may start.
Single signon in the roll-and-scroll
environment is only available for Telnet-based sessions.
Single signon is facilitated on the client side by the Broker Client Agent application (clagent.exe).
Enabling Single Signon
Control of the single signon functionality is maintained and administered on the server for both VISTA client/server applications (i.e., GUI) and the roll-and-scroll environment (i.e., terminal sessions). In support of that functionality a new field, DEFAULT AUTO SIGN-ON, was added to the Kernel System Parameters file (#8989.3) and AUTO SIGN-ON was added to the New Person file (#200). The valid values for these fields are Yes, No, or Disabled.
These new fields, in conjunction with the existing multiple signon fields, give the sites control of the implementation of single signon for users in both the GUI and roll-and-scroll environments. The values in the AUTO SIGN-ON and MULTIPLE SIGN-ON fields in the NEW PERSON file (#200) take precedence over the values in the DEFAULT AUTO SIGN-ON and DEFAULT MULTIPLE SIGN-ON fields in the Kernel System Parameters file (#8989.3). Therefore, the fields in the NEW PERSON file are checked first. If the user fields in the NEW PERSON file are null, the values in the KERNEL SYSTEM PARAMETERS file will be used.
The AUTO SIGN-ON field in the NEW PERSON file and the DEFAULT AUTO SIGN-ON field in the Kernel System Parameters file are initially set to null.
If a user is not allowed multiple signons, they will only be allowed to initiate a single session (i.e., automatically disallowing single signon).
Example 1:
If a user has an active VISTA session and has the following characteristics:
They will be allowed to start another VISTA session without having to re-enter their Access/Verify codes.
Example 2:
If a user has an active VISTA session and has the following characteristics:
They will be allowed to start another VISTA session, however, they must re-enter their Access and Verify codes.
The following table can be used as a guide to control multiple signons and single signon (a.k.a. auto signon) for some typical situations:
| Description | *User Settings | **System Settings |
| Multiple Signon: | ||
| Disallow all users from having multiple signons | No/Null | No |
| Allow individual users to have multiple signons | Yes | No |
| Allow all users to have multiple signons | Yes/Null | Yes |
| Auto Signon:
NOTE: With the exception for disabling auto signon, the following settings are only affective when users are allowed multiple signons. |
||
| Stop auto signon | Any Value | †Disabled |
| Allow individual users to have auto signon | Yes | No |
| Disallow individual users from having auto signon | No | Yes |
| Allow all users to have auto signon | Yes/Null | Yes |
†Sites may choose to disable single signon (stops calls to the Broker Client Agent) for all users in the following situations:
*User Settings refers to the NEW PERSON file (#200) and the following fields:
The User Settings override the System Settings except when disabling single signon!
**System Settings refers to the Kernel System Parameters file (#8989.3) and the following fields: