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 >>
    Using SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Configuring the Client >>
    Authentication >>
        Using the z/OS System Authorization Facility
        Server Authentication with Public Keys in File >>
        Server Authentication with Certificates
            Server Configuration
            Client Configuration
        User Authentication with Passwords
        User Authentication with Public Keys in File >>
        User Authentication with Certificates >>
        Host-Based User Authentication >>
        User Authentication with Keyboard-Interactive >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Examples of Use >>
    Man Pages >>
    Log Messages >>

Server Authentication with Certificates

SSH Tectia Server for IBM z/OS includes two implementations of certificate authentication. One is based on keys and X.509 certificates in files and software cryptography. This is the same implementation that is available in SSH Tectia 4.x products on other platforms. The other is based on keys and certificates managed by the z/OS System Authorization Facility (SAF) and cryptographic operations handled by the z/OS Integrated Cryptographic Service Facility (ICSF) and is new in the SSH Tectia Server for IBM z/OS 5.3 release.

The two implementations may be combined. SAF validation may be complemented with the SSH Tectia 4.x certificate validator and the SSH Tectia 4.x implementation may use trusted keys stored in SAF.

  • SAF Validation

    ICSF is the interface to hardware cryptographic devices. SSH Tectia Server for IBM z/OS benefits from the higher security and performance that these devices provide for keys and certificates managed by SAF.

    SSH Tectia Server for IBM z/OS also supports SAF keys that do not use hardware crypto devices, the so-called NON-ICSF keys. For these keys, the cryptographic operations are performed in software.

    The interface to SAF in SSH Tectia Server for IBM z/OS 5.3 is implemented with an SSH Tectia External Key Provider. The External Key Providers are configured with specification strings in a configuration file or on a command line.

    SSH Tectia Server for IBM z/OS validates public keys by matching them against trusted keys stored in the file system.

    SAF does a limited form of certificate checking that only determines which SAF user is the owner of the certificate. SAF does not check the contents of the certificate, such as the validity period, or check for certificate revocation. Instead of revoking a certificate the site can reduce the user's access rights in SAF.

    A trusted key provider must be configured if SAF certificate checking is to be used.

    To enable SAF checking of remote Secure Shell servers, their certificates can be entered into SAF as SITE keys and placed on a key ring for the trusted key provider.

  • SSH Tectia Certificate Validation

    The SSH Tectia certificate validator does a full validation of the certificate and can be configured to use external PKI services such as LDAP servers that store revocation information.

    When a trusted key provider is configured, the Tectia validator takes its trusted CA certificates from SAF, otherwise they are read from files.

Server Configuration

Client Configuration

PreviousNextUp[Contents] [Index]

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

Copyright © 2006 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