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

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
        Running the Server >>
        Environment Variables for Server and Client Applications
        Setting Up a Shell User>>
            Authenticating Remote Server Hosts
            Using Password Authentication
            Using Public-Key Authentication
        Running Client Programs>>
    Configuring the Server >>
    Configuring the Client >>
    Authentication >>
    File Transfer Using SFTP >>
    File Transfer Using Transparent FTP Tunneling >>
    Tunneling on the Command Line >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Advanced Information >>
    Man Pages >>
    Log Messages >>

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 Server for IBM z/OS:

  • When running SSH Tectia client programs from JCL there is no facility for getting the password from the user. Use public-key authentication and a private key without a passphrase. See Section User Authentication with Public Keys.
  • 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 Section User Authentication with Passwords.

PreviousNextUp[Contents] [Index]


[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2007 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more