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 >>
    Setting up Non-Interactive Server and User Authentication
        Key Distribution Tool
        Authenticating Remote Server Hosts >>
        Using Password for User Authentication
        Using Public Key for User Authentication >>
    Setting up Non-Interactive Secure File Transfer >>

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 Manual.

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 BPXBATCH.

Key Distribution Tool

Authenticating Remote Server Hosts

Using Password for User Authentication

Using Public Key for User Authentication

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