SonicWall Client DPI-SSL feature re-writes the certificate sent by the remote server and signs this newly generated certificate with the certificate specified in the Client DPI-SSL configuration. By default, this is the SonicWall DPI-SSL (CA) certificate. A different certificate can also be specified by importing a signed certificate into the SonicWall. To avoid users from getting certificate trust errors in their browser when visiting a SSL enabled website, the SonicWall DPI-SSL (CA) certificate (or the imported certificate used for re-signing) should be added to the trusted root store of the client machines on the network. In a Windows PKI environment the certificate can be distributed to clients using Group Policy. This article illustrates the method to deploy the Client DPI-SSL re-signing certificate with Group Policy.
NOTE: Some browsers like Firefox do not use the Windows certificate store but have their own certificate store. In such cases, the certificate may have to be manually imported into the browsers' trusted list.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
Downloading the Client DPI-SSL Certificate
Configuring Domain Group Policy
NOTE: To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory or you must have been delegated the appropriate authority.
TIP: For Mozilla Firefox please see their documentation on how to deploy this at the links below:
The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.
Downloading the Client DPI-SSL Certificate
Configuring Domain Group Policy
NOTE: To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory or you must have been delegated the appropriate authority.
TIP: For Mozilla Firefox please see their documentation on how to deploy this at the links below: