Previous Topic: Sample Program Using DIAGNOSE X’A0’ Subcode X’60’Next Topic: Software Requirements for Servers Supporting Traditional Server Validation


Configuring CA VM:Secure to Work with the TCP/IP Feature

This section contains information on how to use CA VM:Secure with the TCP/IP feature of VM for controlling TCP/IP client access to resources owned by the client VM user ID.

IBM supplied TCP/IP server machines, on all versions of VM supported by IBM, allow an external security manager product, like CA VM:Secure, to control access to VM resources by the clients of these server machines. The servers are FTP (FTPSERVE), REXEC (REXECD), NFS (VMNFS), IMAP (IMAP), LP (LPSERVE), and NDB (NDBSRVnn). All of these servers accept a VM user ID and password, and after validation, allow the client access to VM resources accessible by that VM user ID.

The TCP/IP Planning and Customization manual for your release of VM contains an appendix on Using TCP/IP with an ESM, which documents how to configure the servers. That document describes two Server Validation Methods. The traditional method only validates clients having traditional passwords of length eight or less. The enhanced method supports VM password phrases. CA VM:Secure supports both methods. The CA VM:Secure specific information is documented in this chapter. This information is divided into sections for servers supporting traditional server validation, and for servers supporting enhanced server validation. Because servers which currently support traditional passwords only may be enhanced in the future, be sure to consult the TCP/IP server documentation for your release of VM so you can choose the appropriate configuration method.

This section contains the following topics:

Software Requirements for Servers Supporting Traditional Server Validation

Software Requirements for Supporting Enhanced Server Validation

For More Information