Previous Topic: How You Test the Session

Next Topic: Security Features of the SSH-2 Protocol Implementation


Asynchronous SSH Sessions

You can use CA Automation Point to establish up to 175 automated asynchronous session connections using version 2 of the SSH (Secure Shell) protocol (SSH-2). The SSH-2 client protocol implemented by CA Automation Point uses TCP/IP to establish a secure terminal connection to the remote host running a compatible SSH-2 server. You can define this terminal connection using any of the VT series terminal emulators currently supported by CA Automation Point.

Although the SSH-2 protocol defines a suite of applications used to send data securely across a TCP/IP network, CA Automation Point currently allows you only to establish a secure terminal session to the SSH-2 server. This terminal session functionality was designed to closely match the capabilities of the existing CA Automation Point Telnet interface. If you are upgrading from a previous release of CA Automation Point and have Telnet sessions already defined, you should be able to transition these sessions to our SSH-2 client implementation with minimal effort. As part of this design, CA Automation Point currently only supports the user authentication methods that require the user to specify login credentials directly (which mirrors the user authentication used for Telnet sessions). The supported SSH-2 user authentication methods (as defined by both the SSH-2 protocol and additions to the SSH-2 specification) are: "password" and "keyboard-interactive." Both of these user authentication mechanisms require the user to specify a valid login name and optional password to confirm their identity before a terminal session is established.