Certificate tab

Client Certificate

These parameters specify the type of client certificate to use if any. Enable Secure Sockets Layer on the Security tab must be enabled in order for client certificate support to be active.

No Client Certificate: Specifies that a client certificate should not be presented.
Client Certificate in Disk File: Specifies that a client certificate must be presented.
- Certificate File: Specifies the path to the certificate file.
  - View: Click to view the certificate.
  - Browse: Click to locate the certificate file.
- Private Key File: Specifies the path to the private key file.
  - Browse: Click to locate the private key file.
Client Certificate in Certificate Store: Specifies that a client certificate must be presented that is located in the certificate store.
- Common Name: Specifies the path to the common name file.
  - View: Click to view the certificate.
  - Browse: Click to display a list of certificates in the certificate store.
Client Certificate in Certificate on Smart Card: Specifies that a client certificate stored on a Smart Card must be presented. This feature is currently not implemented.

Root Certificates

These parameters specify the root certificate store to use: the one provided by OpenSSL or the one provided by Windows.

Use OpenSSL Root Certificates: (Default) If selected, the root certificates provided by OpenSSL are used.
Use Windows Root Certificates: If selected, BlueZone looks for a file called rootcerts.pem in the end user's bluezone\certs directory. If it doesn't exist, it automatically exports the root certificates from Windows and store them there, giving a message such as ''109 root certificates were exported.''
- Update Root Certificates: Click to manually export the certificates. If you connect and are presented with an untrusted host root certificate, check the box to add it to the trusted list, it imports it into the Windows root store (which can produce a Windows message asking for confirmation) and then export the root store again to disk producing a message such as ''109 root certificates were exported.'' When this is performed one time, subsequent connections connect without messages.