Security

Topics

• Security Features
• Validation of Connection Request
• Validation of Users
  • Users Can Customize Signon Window
  • Change VISTA Verify Code Component
• Validation of RPCs
• Sample Security Procedures
• Security Features Tasks Summary

Security Features

Security in distributed computing environments, such as in client/server systems, is much more complicated than in traditional configurations. Although it is probably impossible to protect any computer system against the most determined and sophisticated intruder, the RPC Broker implements robust security that is transparent to the end user and without additional impact on IRM.

Security with the RPC Broker is a four-part process:

1. Client workstations must have a valid connection request
   
   
1. Users must have valid Access and Verify codes
   
   
1. Users must be valid users of a VISTA client/server application
   
   
1. Any remote procedure call must be registered and valid for the application being executed

Validation of Connection Request

An enhancement to security has been included with this version of the Broker. Before the Broker Listener jobs off a Handler for a client, it checks the format of the incoming connection request. If the incoming message does not conform to the Broker standard, the connection is closed. This serves as an early detection of impostors and intruders.

Validation of Users

The GUI signon application is integrated with the RPC Broker interface. This GUI signon is invoked when the client application connects to the server. The signon application automatically prompts users for their Access and Verify codes if they are not already signed on to a VISTA application.

A sample of the GUI signon window integrated with the RPC Broker is illustrated below:

This version of the Broker supports single signon. For more information regarding single signon, please refer to the description in Kernel Patch #59 (i.e., XU*8*59).

Client/server applications are a "B" (i.e., Broker) type of option in the OPTION file (#19). Users must have the client/server application option assigned to them like any other assigned option in VISTA. It can be put on their primary menu tree or as a secondary option/menu as part of their suite of permitted options. The client/server application will only run for those users who are allowed to activate it.

The client/server application options will not be displayed in a user's menu tree.

Kernel's Menu Manager verifies that users are allowed access to a VISTA application or option with the following process:

1. Users start a VISTA program.
   
   
2. The RPC Broker in the client application invokes the GUI signon when connecting to the server.
   
   
3. Users sign on to the server via the Kernel signon process (see the Signon window dialog box).
   
   
4. If authorized, the user is granted access to the server, otherwise an error message is returned. This serves as an initial security check.

For more information on Access and Verify codes or the Kernel signon process in general, please refer to the Kernel Systems Manual.

Users Can Customize Signon Window

When a VISTA program on the client connects to the server, the VISTA signon window is displayed for the user to identify and authenticate himself on the server. This window's System menu (i.e., see the upper left corner of the Signon window dialog box) has a "Properties..." item:

When this item is selected, the user is presented with the following configuration dialogue box:

Using the Sign-on Properties dialog box, users can control the appearance of the signon window by modifying the following characteristics:

• Position of the signon window
• Size of the signon window
• The appearance of the introductory text

Window Position

The window position can be one of the following:

Window Size

The window size can be one of the following:

Introductory Text

The introductory text has a couple of settings users can control:

Background Color:

Font:

When users press the "Change Font" button they are presented with a Font form that can be used to change the font face, style, size, and color of the introductory text of the signon window.

Change VISTA Verify Code Component

This version of the Broker includes a new Change VISTA Verify Code dialog for the client workstation. After a user signs onto the server, if their Verify code has expired, the user is automatically prompted with the following message: "You must change your Verify code at this time." Once the user presses the OK button they are presented with the Change VISTA Verify Code window as displayed below:

The old Verify code will appears as asterisks (*) in a grayed-out box.

Users must then do the following:

• Enter their new Verify code
  
  
• Confirm their new Verify code

In the future, users will be able to invoke this dialog whenever they choose to modify their Verify code. For now, users who wish to change their Verify code prior to expiration may do so via the Edit User Characteristics option in the roll-and-scroll environment.

Validation of RPCs

The RPC Broker security allows any RPC to run when it is properly registered to the VISTA client/server application. The Broker on the server along with the Kernel's Menu Manager determines which application a user is currently running. Menu Manager determines if a user is allowed to run this application or option by the following process:

1. A remote procedure call is sent by a client application and is received by the RPC Broker on the server.
   
   
2. The Broker verifies that the RPC is "registered" to the application that the user is currently running, prior to executing the remote procedure call (RPC).

   The application being run is designated by a "B"-type option in the OPTION file (#19). The application must specify the option and that option must be in a user's menu tree.

   
   

   For more information on registering an RPC to a package, see the topic entitled "RPC Security: How to Register An RPC" in the RPC Broker V. 1.1 Getting Started with the Broker Development Kit manual.

   
   
   
3. Menu Manager checks if the RPC is registered for this package option. If not properly registered, Menu Manager will return a message explaining why the RPC is not allowed.
   
   
4. The Broker on the server executes the RPC if it is registered, otherwise it is rejected.

Sample Security Procedures

The security steps each client user will follow and the intermediate client/server security processes are described in the following example:

Security Features Tasks Summary

The following table summarizes the security tasks that are required and which module completes them:

To reiterate, an RPC is only allowed to run within the context of an application with which it is registered. Users are only able to run the server side of the application that was installed on the server by IRM.

For each release of the RPC Broker, the RPC Broker Development Team will continuously strive to implement the most complete, robust, and flexible security available at the time.