Barracuda Authentication - Barracuda Networks NG Network Access Client SP4 Administrator's Manual

10.6.5

Barracuda Authentication

Barracuda Authentication requires a valid certificate file (*.lic). The .lic file must be saved locally on the client
system using it.
The following parameters are available for Barracuda Authentication:
List 10–1 Parameters used with Barracuda NG authentication
Parameter Description
File Select the certificate (*.lic) file needed for authentication at the VPN server.
Hash READ-ONLY
After a certificate has been loaded, its hash is displayed in this field.
Certificate File Only editable if a certificate file has been loaded.
Password The password for certificate usage can be changed here. Enter the new password and confirm it.
The creation of a Barracuda Authentication related profile can be rudimentary adapted by including an .ini file into the
creation process. If you want to make use of this option, then have a look at 10.6.8 Advanced Settings Tab, page 143
first. Subsequently, refer to 10.6.9 Adaptation of Profile Creation using an .ini file (Barracuda NG Authentication only),
page 146 for further details.
10.6.6 X509 Authentication
The following parameters are available for X509 authentication:
Selecting this method requires a valid X.509 certificate (*.).
List 10–2 Parameters available for use with X509 authentication
Description
Subject
Issuer
Use serial number
Valid to
Key specific
Key usage
Private Encrypt
Prompt for user and password
Temporary Root Certificate
Show external X509 Certificate
142 VPN Component Configuration
Description
After the X.509 certificate has been selected, its subject is displayed here.
Displays the issuer of the selected X.509 certificate.
Defines if the certificate's serial number gets used in the authentication process.
Displays date and time when the X.509 certificate looses validity.
Hash value of the certificate file.
Value of the KeyUsage keyCertSign bit. Possible values are Exchange (public key exchange) or Signing (digital
signature).
Switches encryption procedure (private key for encryption, public for decryption) depending on whether crypto API
is supported or not.
Set to yes to request both, certificate and user/password validation.
As soon as a temporary root certificate has been provided by the server, it can be viewed with the menu item
Show ... or deleted with the menu item Clear.
If an external X.509 certificate has been loaded, its properties can be viewed here.