Description

When trying to initiate a connection with Clavister OneConnect Client you may get the following error.

Windows: Server certificate is not trusted by Windows
iOS: Invalid certificate format

Background

Certification validation is done in several steps.

• First Client initiates a connection to the configured NetWall (vpnserver.mydomain.com). 
• Next, the Netwall presents it's system certificate. The subject field needs to contain the correct DNS name(s) (FQDN), either vpnserver.mydomain.com (or *.mydomain.com when using a wildcard certificate).
• If the first two steps are successful the certificate will be checked against the clients system certificate store.

If there is a mismatch (for example you enter the IP address instead of the FQDN, or the certificate is not trusted) you get the described error.

Common Windows VPN client Errors that are related to certificate mismatch

• Windows: Server certificate is not trusted by Windows.
• Windows: Server Certificate is not valid for the requested usage. This error is also returned if the certificate has an invalid name.

Solution

1. Make sure that your certificate fits the requirements and has the correct FQDN
2. Import the certificate incl. private key in your NetWall under /Objects /General /Key Ring. Type must show as Local.
3. Select the certificate as HTTPS certificate under /System /Device /Device Settings /Remote Management → /Advanced Settings
   Be aware that this is also the certificate of your Web-User-Interface!
4. Import the certificate to your clients system certificate store.
   1. If the certificate is bought from a well-known CA authority you should be able to skip this step, as your computer already trusts the according CA.
   2. If the certificate is self-signed then you need to import it on all clients using OneConnect. Please follow the documentation of your operating system on how to do this.
      1. Note: The private key should not be exported.

Using public certificates in Clavister NetWall (cOS Core) for OneConnect

If you want to use a public certificate for your clients, please refer to the following article in this Knowledge Base: Configuring public certificates in NetWall firewalls

Using self-signed certificates in Clavister NetWall (cOS Core) for OneConnect

 An example on how to generate a self-signed certificate from Cos Core itself.

1. Navigate to Object->Key Ring
2. Click the drop-down menu Add->Certificate
3. Provide a name to the Certificate (eg., Oneconnect_160)
4. Under Generate Certificate Sub-menu ->Click Configure->It will open a Certificate Generator Pop-Up window.

     5. Select the Certificate Type as Self-Signed.

     6. Provide the Subject Name and Subject Alternative Name along with Key size and Type details.

         Example:

• Subject name = CN=Clavister
• Subject Alternative Names = 10.122.137.160
• Public Key Type : RSA or EC
• Key Size : 2048 bits
• Signature Algorithm : SHA-256
• Validity : 365 days 

   7. Click Generate.

   8. Once when the certificate is successfully generated, verify and download.

Important: Client hostname must match certificate hostname

A specific requirement when using certificates with the OneConnect Interface is that the

hostname value entered into the clientmust be the same as either the Common Name

(CN) or one of the Subject Alternative Name (SAN) options in the certificate used by the

cOS Core OneConnect Interface**.

Note that the One connect VPN client profile must be specified with a IP Address or a FQDN that matches with the certificate in the Cos Core.

The above image is taken from the Windows One connect VPN client

    9. Select the certificate as HTTPS certificate under /System /Device /Device Settings /Remote Management → Advanced Settings.

  10. Import the certificate to your client system certificate store.

Additional Notes

Certificate validity period max. one year

If you are using public certificates, please make sure that they are valid no longer than one year. SSL/TLS certificates issued after September 1, 2020 with a validity period greater than 398 days will not be trusted by Apple’s Safari browser and iOS/iPadOS/ devices for security reasons.

Self-signed certificates should not be affected by this rule as per today. But that could change anytime.

Related articles