Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

User Authentication Settings

SSH Tectia Servers need to perform the following actions for strong user authentication:

  • Validate the user certificate signature. For this, the CA certificate is needed.

  • Verify that the user certificate has not been revoked. In this case, the check is performed against a CRL retrieved from the LDAP directory configured in LDAP Server URL.

  • Authorize the login using rules that map certain fields of the user certificate to existing user accounts on the server host. The Certificate selectors are defined in Server configuration Authentication Settings.

Depending on the security policy and PKI environment of the end-user organization, other settings may be required in actual deployments (for example, certificate caching in case of large CRLs).

The CA certificate is imported into the Management Server prior to deploying the configuration to the hosts. Other PKI-related settings are entered via the SSH Tectia Manager administration interface and stored on the Management Server, in a manner similar to other SSH Tectia Server settings.

The user authentication settings are done on tab Configurations → Edit Configurations → SSH Tectia under the Server configuration PKI view.

The enrollment settings for the internal CA settings are made on tab Configurations → Edit Configurations → PKI.

For examples of the user authentication settings on SSH Tectia Server, see Figure 5.19, and on the internal CA enrollment settings, see Figure 5.20.

User authentication settings

Figure 5.19. User authentication settings

Adding a CA certificate for User authentication

Figure 5.20. Adding a CA certificate for User authentication

Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps