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 >>
    Transferring Files >>
    Tunneling >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Advanced Information >>
    Man Pages >>
    Log Messages >>

Setting Up a Shell User

Users that are going to use SSH Tectia Server for IBM z/OS from a remote host must have an OMVS segment in their RACF profile. In addition, if a user is going to access the USS shell or execute USS shell commands or run SSH Tectia Server for IBM z/OS client programs on the mainframe, the user must have a home directory in the USS file hierarchy. The requirements are the same as for accessing USS with Telnet on port 1023.

z/OS users that are going to use the SSH Tectia Server for IBM z/OS client programs to access remote hosts need the same OMVS environment.

If you want to customize the environment per user for file transfer use, see Section File Transfer Environment Variables.

Authenticating Remote Server Hosts

Using Password Authentication

Using Public-Key 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