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.

Tectia

Permission Requirements

The following permissions are required for installing and running Tectia Server for IBM z/OS:

File system requirements

Write access to the /opt directory is required during the installation.

User account requirements for installing the server
  • The setup script uses the extattr command to make the server program, /opt/tectia/sbin/sshd2, program- controlled. To issue the command, the user account running the setup must have read access to the BPX.FILEATTR.PROGCTL facility.

  • The user account running the setup must have an OMVS segment and the UID 0.

User account requirements for running the server

It is recommended that a user account, SSHD2, is created for running Tectia Server for IBM z/OS, see Section Creating the SSHD2 User:

  • The user account running the server must have an OMVS segment and the UID 0.

  • If the BPX.DAEMON FACILITY class profile is defined, the user must have read access to it.

Requirements for user accounts to support access via Tectia Server
  • Required: An OMVS segment

  • Optional: A home directory. It is required if public key user authentication is used or if the account requires user-specific configuration, for example, environment variables for the file transfer subsystem.

Requirements for user accounts that run Tectia client programs
  • Required: An OMVS segment

  • Optional: A home directory. It is required if public key user authentication is used or if the account requires user-specific configuration, for example, profiles for remote hosts.

Library requirements
  • CEE.SCEERUN and CEE.SCEERUN2 libraries must be available in LPALIB or LNKLST.

  • CEE.SCEERUN2 must be program-controlled.

TCP permissions

The server must be allowed to listen to port 22 (or other configured Secure Shell port).

Permissions for storing keys in SAF

If the server host key or the user keys are going to be stored in the System Authorization Facility (SAF), additional permissions are required.

===AUTO_SCHEMA_MARKUP===