Skip to main content
yzRad
New Member
February 9, 2022
Solved

Best Practice dealing with 3rd party certificates to allow SSL connection

  • February 9, 2022
  • 1 reply
  • 2057 views

Hi ,

 

I'm not familiar with Fortinet at all. 

 

I would like to understand what is the best practice when we need to enable a connection 

to a site like Github and such .

Since the certificate copy  produced by Fortinet replacing the original Github  certificate isn't valid 

by the client and we get a SSL error.

 

So how do we deal with such a situation ? i.e allowing SSL connection to Github ( as an example ).

 

I would be much obliged if you could answer me as to a completely noob.

Thanks

 

 

Best answer by kcheng

Hi,

 

I believe you are using deep inspection where the certificate is replaced with FortiGate certificate. In that case, you will need to import the FortiGate certificate into client's machine and configure it as trusted CA. Kindly refer to the following document:

Cookbook | FortiGate / FortiOS 6.2.0 | Fortinet Documentation Library

 

1 reply

kcheng
Staff & Editor
kchengAnswer
Staff & Editor
February 10, 2022

Hi,

 

I believe you are using deep inspection where the certificate is replaced with FortiGate certificate. In that case, you will need to import the FortiGate certificate into client's machine and configure it as trusted CA. Kindly refer to the following document:

Cookbook | FortiGate / FortiOS 6.2.0 | Fortinet Documentation Library