For the VPN service, you can use either self-signed certificates or certificates that are generated by an external CA.
In this article:
Before You Begin
Before you set up VPN certificates, verify that the VPN service has been properly created and configured. For more information on how to create a service, see How to Configure Services.
Set Up Certificates with the Barracuda CA for a Barracuda VPN
If you want to use a Barracuda VPN with the Barracuda CA installed on the Barracuda NextGen Firewall F-Series, complete the following steps:
Step 1. Create the Default Certificate and Private Key
The default server certificate will be signed by the self-signed Barracuda root certificate that is included with the Barracuda NextGen Firewall F-Series.
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- Click the Settings tab.
- Click the Click here for Server Settings link.
- If you are using the Access Control service, enter its IP Address in the Access Control Service section of the Server Settings window.
- Create the certificate:
- In the Default Server Certificate section, click Ex/Import and select New/Edit Certificate.
In the Certificate View window, fill out the Subject section completely. You must set the SubAltName and Name to the FQDN resolving to the listening IP address of the VPN service.
Click OK.
- Create the default key:
- Click Ex/Import in the Default Key section.
- Select New x-Bit RSA key (where x is 512, 1024, or 2048).
- Click OK.
- Click Send Changes and Activate.
Step 2. Import the Default Certificate and Private Key
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- Click the Settings tab.
- Click the Click here for Server Settings link.
- If you are using the Access Control Service (NAC), enter its IP Address in the Access Control Service section of the Server Settings window.
- In the Default Server Certificate section, click Ex/Import and select either Import PEM from file or Import from PKCS12, depending on the external certificate format.
- In the Default Key section, click Ex/Import and select Import Private Key from File.
If the certificates match, the Default Server Certificate and the Default Server Key display 'Valid' in green. - Click OK.
- Click Send Changes and Activate.
Set Up Certificates with an External CA for a Barracuda, IPsec, or L2TP/IPsec VPN
Requirements
X.509 Certificate Type | Install Location | File Type | Chain of Trust | X.509 Extensions and Value |
---|---|---|---|---|
Root Certificate, for example, RootCrt.crt | Barracuda NextGen Firewall F-Series | PEM | Trust Anchor |
|
Server Certificate, for example, ServerCrt.pem and ServerCrtprivate.pem | Barracuda NextGen Firewall F-Series | PKCS12 | End Instance |
|
Client Certificate, if needed | Client OS or VPN Client | PKCS12 | End Instance |
|
Install the Root Certificate
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- Click the Root Certificates tab.
- Right-click the table and select Import PEM from File or Import CER from File, depending on the root certificate format.
- In the Open window, select the root certificate file and click Open.
- In the Root Certificate window, configure the following settings under the Certificate details tab:
- Name – A descriptive name for the root certificate. For example, RootCert.
- Usage – The types of VPNs that will use this root certificate. For example, Barracuda Personal and IPsec Personal.
- Click OK.
The root certificate appears under the Root Certificates tab.
Install the Server Certificate
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- Click the Server Certificates tab.
- Import the server certificate.
- Right-click the table and select Import Certificate from File.
- In the Open window, select the server certificate file and click Open.
- Enter the Certificate Name, for example,
ServerCertificate
, and then click OK. The certificate appears under the Server Certificates tab.
- Import the private server key.
- Right-click the server certificate and select Import Private Key From File.
- In the Open window, select the private server key file, for example, ServerCertprivate.pem, and then click Open.
- Click Send Changes and Activate.
Your server certificate appears with the private key in the Server Certificates list.
Create a Service Certificate/Key
- Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN-Service > VPN Settings.
- Click Lock.
- Click the Service Certificates/Keys tab.
- Right-click the table and select New Key.
- Enter a Key Name, and click OK.
- Select the required Key Length, and click OK.
- Click Send Changes and Activate.
Your service certificate appears under the Service Certificates/Keys tab.
Create a CSR on the Barracuda NextGen Firewall F-Series
You can create a certificate signing request (CSR) directly on the command line of the Barracuda NextGen Firewall F-Series.
- Go to SSH and login.
On the command line enter:
openssl req -new -newkey rsa:2048 -nodes -keyout domain.key -out domain.csr
Download the certificate to your desktop:
[down] domain.csr
- Save the csr file to your disk.
You can now submit the certificate signing request to your CA to receive a signed certificate.
Certificate Detail Settings
From the Certificate details tab, you can configure the following settings:
- Certificate – The certificate's subject and issuer.
- Name – The certificate name for easier recognition.
- Usage – The tunnel types that the certificate is valid for. The following tunnel types are available:
- Personal
- Site-to Site
- IPSec Personal
- IPSec Site-to-Site
- Comment – An optional description of the certificate.
- Timeout (min.) – The length of time after which the fetching process is started again if all URIs of the root certificate fail.
- Action – The action that is taken if the CRL is not available after the fetching process that is started after the Timeout. You can select one of the following actions:
- Terminate all sessions – Every VPN session relating to this root certificate is terminated.
- Do not allow new sessions – New VPN sessions relating to this root certificate are not allowed.
- Ignore – A log entry is created but does not have any effect on VPN connections relating to this root certificate.
Certificate Revocation Settings
From the Certificate details tab, you can either import or manually add a CRL URI.
- If a CRL is already included within the certificate, import the CRL URI by clicking Load paths from certificate.
- To add a CRL URI manually, configure the settings in the URI, Login, and Proxy sections and then click Add.
- Protocol – The required connection protocol. The following protocols are available:
- LDAP – DNS-resolvable, default port: 389
- LDAPS – DNS-resolvable, default port: 636
- HTTP – Default port: 80
- HTTPS – Default port: 443
- Host – The DNS-resolvable host name or IP address of the server that makes the CRL available.
URL-Path – The path to the CRL. For example:
cn=vpnroot,ou=country,ou=company,dc=com?,cn=*
- User / Password – The username and corresponding password. This information is necessary if the LDAP or HTTP server requires authentication.
- Proxy – The DNS-resolvable host name or IP address of the proxy server.
- Port – The proxy server port used for connection requests.
- User / Password – The username and corresponding password. This information is necessary if the proxy server requires authentication.
From the OCSP tab, you can configure the following settings:
- Host – The DNS-resolvable hostname or host IP address.
- Port – The OCSP server listening port. Use SSL – Enforces an SSL connection to the OCSP server.
- Phibs Scheme – Allows selection of an OCSP scheme (default: ocsp). CA Root – Specifies how the OCSP server is verified. You can select the following options:
- This root certificate – The OCSP server certificate signing the OCSP answer was issued by this root certificate.
- Other root certificate – The OCSP server certificate signing the OCSP answer was issued by another root certificate. This other root certificate must be imported via the Other root setting.
- Explicit Server certificate – The OCSP server certificate signing the OCSP answer might be self-signed or another certificate. This X.509 certificate must be imported via the Explicit X.509 setting.
- Other root – If CA Root is set to Other root certificate, click Ex/Import to import the certificate in either PEM or PKCS12 format.
- Explicit X509 – If CA Root is set to Explicit Server, click Ex/Import to import the certificate in either PEM or PKCS12 format.