Why is the VPNease web UI certificate reported as invalid by my browser?
VPNease server uses the HTTPS (HTTP over SSL) protocol for ensuring confidentiality of data between the browser and the server. HTTPS requires the server to be authenticated by a certificate. To ensure security, each VPNease needs to have a distinct certificate created when the product is installed. Dynamically generated certificate cannot have certification from a certificate authority such as Thawte or Verisign. Instead, the certificates are self-signed, presented “as is” as proof of identity. Another issue is that the server certificate contains a Common Name field, which should ideally match the domain name of the server. However, because a VPNease server can be accessed by both domain name(s) and often multiple addresses, the Common Name is set to a neutral unique value instead. When your browser reports an untrusted certificate from a VPNease server, you should first ensure that your connection to the server is secure (e.g. you are in your company intranet), and then add the cert
Related Questions
- What error message appears in the Web browser if an effective CRL cannot be obtained? Is the same error message displayed if the CRL is obtained and if the certificate is revoked?
- When using my SSL certificate from Verisign, then the web browser complains that the parent certificate expired. Do I need a new certificate?
- My web browser is reported as incompatible. Can I still access NEIUport?
