Setting up Non-Interactive Server and User Authentication
The Secure Shell protocol used by SSH Tectia Server for IBM z/OS provides mutual authentication
– the client authenticates the server and the server authenticates the
client user. Both parties are assured of the identity of the other party.
The Secure Shell server host can authenticate itself using either
traditional public-key authentication or certificate authentication.
The Secure Shell client users can authenticate themselves using password,
public-key, keyboard-interactive, or host-based authentication. These
authentication methods can be combined or used separately, depending on the
level of functionality and security you want.
This chapter gives instructions for setting up non-interactive
authentication for server and users using public keys. For information
on the other authentication methods, see SSH Tectia Server for IBM z/OS Administrator
Most of the examples in this chapter are executed from Unix shell (for
example, OMVS shell), but the same commands can also be run in JCL using