Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server (M) >>
    Using SSH Tectia Server (M) >>
        Configuration Files>>
        Running the Server >>
        Setting Up a Shell User
            Authenticating Remote Hosts
            Using Password Authentication
            Using Public-Key Authentication
        Running Client Programs>>
        Handling MVS Datasets>>
        File Transfer Examples>>
    Troubleshooting SSH Tectia Server (M) >>
    Configuration >>
    Authentication >>
    Application Tunneling >>
    Sample Files >>
    Man Pages
    Log Messages >>

Setting Up a Shell User

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

z/OS users that will use the SSH Tectia Server (M) client programs to access remote hosts need the same OMVS environment.

The ADDUSER job creates a new user profile and a home directory (see Appendix ADDUSER).

Note: The job deletes any existing profiles.

Note: See the chapter Environment Files on how to control file transfer.

Authenticating Remote Hosts

Using Password Authentication

Using Public-Key Authentication

PreviousNextUp[Contents] [Index]

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

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