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

SSH Tectia

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.

There are two cases where it cannot be used in SSH Tectia client tools for z/OS:

  • When running SSH Tectia client programs from JCL there is no facility for getting the password interactively from the user. You can set up password in a file or dataset, or preferably use public-key authentication and a private key without a passphrase. See Password in File or Dataset and User Authentication with Public Keys in File.

  • Password authentication is not available when running SSH Tectia client programs from the TSO OMVS shell because the shell cannot guarantee that the password will be hidden on the screen. Use a Telnet shell or Secure Shell, or set up public-key authentication using a private key without a passphrase.

For more information on password authentication, see User Authentication with Passwords.


 

 
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