SSH

Chapter 5 Authentication

Table of Contents

Supported User Authentication Methods
Server Authentication with Public Keys
Server Authentication with Certificates
Server Authentication Using External Host Keys
User Authentication with Passwords
User Authentication with Public Keys
User Authentication with Certificates
Host-Based User Authentication
User Authentication with Keyboard-Interactive
User Authentication with GSSAPI
Supplementing Authentication with an External Application
Configuring User Authentication Chains
Forwarding User Authentication
Reporting User Login Failures
User Name Handling on Windows
Requirements for Trusted Domain Authentication on Windows
Accessing Resources on Windows Network from Logon Sessions Created by Tectia Server
Accessing Files Stored on EFS on Windows from Logon Sessions Created by Tectia Server

The Secure Shell protocol used by the Tectia client/server solution provides mutual authentication – the client authenticates the server and the server authenticates the client users. Both parties are assured of the identity of the other party.

The Tectia Server host can authenticate itself to the client using either public-key authentication or certificate authentication.

Different methods can be used to authenticate Secure Shell client users. These authentication methods can be used separately or combined, depending on the level of functionality and security you want. The server defines what methods are allowed, and the client defines the order in which they will be tried. The least interactive methods should be tried first. In case several interactive authentication methods are defined for user authentication, the client-side will alternate between the methods on each failed authentication attempt.

User authentication methods

Figure 5.1. User authentication methods


Tectia Server allows GSSAPI, public-key, keyboard-interactive, and password in user authentication by default.