![fortinet vpn client chromebook fortinet vpn client chromebook](https://1.bp.blogspot.com/-1vTczC1ZI_g/XoFxpeEZPcI/AAAAAAAAA6A/XlvPS5L7ONElT4KpikgHuI9BzgYl6Ek1wCLcBGAsYHQ/s1600/P4I4.png)
![fortinet vpn client chromebook fortinet vpn client chromebook](http://windowclever351.weebly.com/uploads/1/2/6/6/126682186/593560405.png)
To prevent users from seeing certificate warnings, you can install this certificate on users’ devices. This certificate is also used in the default deep-inspection profile. To avoid encouraging this habit, you can prevent the warning from appearing in the first place.įind this recipe for other FortiOS versionsĥ.2 | 5.4 | 5.6 Using the default certificateĪll FortiGates have a default certificate that is used for full SSL inspection. Often, when users receive security certificate warnings, they simply select Continue without understanding why the error is occurring. This is the same process used in “man-in-the-middle” attacks, which is why a user’s device may show a security certificate warning.įor more information about SSL inspection, see Why you should use SSL inspection. The FortiGate then re-encrypts the content, creates a new SSL session between the FortiGate and the recipient by impersonating the sender, and sends the content to the end user. When full SSL inspection is used, your FortiGate impersonates the recipient of the originating SSL session, then decrypts and inspects the content. This recipe explains how you can prevent certificate warnings when you are using your FortiGate’s default certificate. There are several methods for doing this, depending on whether you are using your FortiGate’s default certificate, a self-signed certificate, or a CA-signed certificate. In this recipe, you will prevent users from receiving a security certificate warning when your FortiGate performs full SSL inspection on incoming traffic.