Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
The Secure Shell protocol used by the SSH Tectia client/server solution provides mutual authentication – the client authenticates the server and the server authenticates the client. 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.
Different methods can be used to authenticate Secure Shell client users. These authentication methods can be combined or used separately, depending on the level of functionality and security you want.
Figure : Secure Shell user authentication methods. Note that all of the methods are not available on z/OS.
The SSH Tectia client on z/OS uses the following user authentication methods by default (in order): public-key, keyboard-interactive, and password authentication. In addition, the client supports host-based authentication.
The SSH Tectia server on z/OS allows public-key and password authentication by default. In addition, the server supports keyboard-interactive and host-based authentication.