SSH Tectia

Defining User Authentication

Select user authentication methods as described in Managing Keys and Certificates and Managing Key Providers.

Managing Keys and Certificates

In this view you can add key and certificate files used in user authentication, generate a new key, or change the passphrase for a key.

Defining keys and certificates

Figure 4.22. Defining keys and certificates

Default keys

The default location of user keys.

Default certificates

The default location of user certificates.

Directories

Use the Add... button to add a directory of keys, Delete to remove.

Files

Select a key from the list and click Change passphrase... to change the passphrase.

Click Upload... to upload the key to a server.

Click New key... to start the key generation wizard. Click the Help buttons in the wizard for more information.

Use the Add... button to add single keys and certificates, Delete to remove.

Managing Key Providers

Available key providers are MSCAPI, Entrust, and PKCS#11.

Defining key providers

Figure 4.23. Defining key providers

Microsoft Crypto API

SSH Tectia can access keys via Microsoft Crypto API (MSCAPI).

Microsoft Crypto API (MSCAPI) providers can be enabled by selecting the Enable Microsoft Crypto API check box. If you enable the MSCAPI providers, you can use software keys and certificates created by Microsoft applications.

Entrust

Select the Enable Entrust check box to enable using Entrust.

Enter the Initialization file (*.ini) and Profile file (*.epf).

By using the Entrust provider, SSH Tectia Client/Connector can utilize keys and certificates stored in an Entrust profile file (.epf). The initialization file includes the basic Entrust PKI configuration (for example the CA address).

When the provider is enabled for the first time, Entrust Entelligence will prompt for your Entrust password. As long as the Entrust provider is enabled, the password is asked each time SSH Tectia Client/Connector is started.

PKCS#11

Click Add... to define a PKCS#11 provider.

Defining a PKCS#11 provider

Figure 4.24. Defining a PKCS#11 provider

Dynamic library

Define a dynamic library containing the PKCS#11 driver.

Slots

Define slots. A slot is a logical reader that potentially contains a token. Slots are manufacturer-specific. They are defined with an integer. Examples: "0,1", "0-3, !2", "2".