Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
SSH Tectia Server can accept both X.509 certificates and Entrust certificates for authenticating users.
To configure the server to allow user authentication with certificates, perform the following tasks:
Acquire the CA certificate and copy it to the server machine. You can either copy the X.509 certificate(s) as such or you can copy a PKCS #7 package including the CA certificate(s). Certificates can be extracted from a PKCS #7 package by specifying the -7 flag with ssh-keygen2.
Certificate authentication is a part of the publickey authentication method. Make sure that you have enabled it in the sshd2_config file:
Specify the CA certificate and the mapping file(s) in the ssh_certd_config file:
You can disable the use of CRLs by adding the PkiDisableCRLs keyword below the Pki keyword.
Note: CRL usage should only be disabled for testing purposes. Otherwise it is highly recommended to always use CRLs. You can define several CA certificates by using several Pki keywords.
Note that multiple MapFile keywords are permitted per Pki keyword. Also, if no mapping file is defined, all connections are denied even if user certificates can be verified using the defined CA certificate. The server will accept only certificates issued by defined CA(s).
Also define the LDAP server(s) in the ssh_certd_config file.
If necessary, define also the SOCKS server in the ssh_certd_config file.
The SOCKS server must be defined if CA services (OCSP and CRLs) are located behind a firewall.
Next you need to create the certificate user mapping file. The map file specifies which certificates authorize logging into which accounts. The format of the file is the following:
<account-id> <keyword> <argument>
The keyword can be either Email, Subject, SerialAndIssuer, EmailRegex, or SubjectRegex. The argument depends on the keyword.
Email: The argument is the e-mail address which must be present in the certificate.
Subject: The argument is the required subject name in LDAP DN (distinguished name) string format.
SerialAndIssuer: The argument is the required serial number and issuer name in LDAP DN string format, separated by spaces or tabs.
EmailRegex: The argument is the regular expression which must match an e-mail address in the certificate. If account-id contains the string %subst%, it is substituted with the first parenthesized part of the regular expression. The patterns are matched using the egrep syntax.
SubjectRegex: The argument is the regular expression which must match a subject name in the certificate. If account-id contains the string %subst%, it is substituted with the first parenthesized part of the regular expression. The patterns are matched using the egrep syntax.