Your browser does not allow storing cookies. We recommend enabling them.

SSH

Using Password Authentication

Password authentication is the most commonly used form of user authentication. It is enabled by default and uses the RACF system password of the user.

Note that when running Tectia client programs from the TSO OMVS pseudo-shell, the password that you type in will be shown on your screen in plaintext. To avoid showing the password on the screen, instead use a real shell via telnet or SSH, or set up public-key authentication using a private key without a passphrase.

There is one case where password authentication cannot be used in Tectia Server for IBM z/OS: When running Tectia client programs from JCL there is no facility for getting the password interactively from the user. You can have the password stored in a file or a data set, or preferably use public-key authentication and a private key without a passphrase (see User Authentication with Public Keys in File).

For more information on password authentication, see User Authentication with Passwords and Tectia Server for IBM z/OSUser Manual.


 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now