Skip to main content
x_member
New Member
Nov 16, 2017 3:55 PM UTC
Question

SSL Inspection policy failing to use new certificate

Fortigate 60D v5.2.11

 

We've had cause to re-issue the certificate that we use for deep inspection on outbound traffic (moving from SHA-1 to SHA-256). This certificate has been installed as trusted on all affected internal clients.

 

To try and ensure a smooth transition, I've installed the new certificate and set it for use in a cloned copy of the outbound deep inspection SSL inspection policy, leaving the original SHA-1 certificate used by the original outbound inspection policy.

 

I've switched one of the firewall rules for traffic to use the new SSL inspection policy with the SHA-256 certificate. 

That was 50 minutes ago, however the fortigate is still utilising the original SHA-15 certificate for inspection (as checking any inspected HTTPS website certificate chain confirms). This behaviour is replicated across multiple clients and browsers (IE11, Chrome, Firefox).

 

I'm assuming that the Fortigate has cached the old certificate. 

Rebooting the firewall is not an option.

How do I 'encourage' the firewall to respect this configuration change and begin using the new SHA-256 certificate to inspect outbound traffic? Is there a process I can restart without interfering with other functionality / traffic?

 

 

    18 replies

    tanr
    New Member
    Nov 16, 2017 4:14 PM UTC

    I think clearing the ssl certificate cache is done with

     

    diag test app ssl 12

     

    Details at http://kb.fortinet.com/kb/viewContent.do?externalId=FD32679

     

    x_member
    x_memberAuthor
    New Member
    Nov 16, 2017 4:52 PM UTC

    Unfortunately 

    diagnose test application ssl 0
    is rejected as a command parse error.

     

    Substituting 'debug' for 'test' and trying 0, 12, and 99 options returns no error in the CLI and no output.

    Symptoms remain unchanged with the certificate chain showing the 'old' SHA1 certificate.

     

     

    I'm not sure the ssl application is present anymore (per https://forum.fortinet.com/tm.aspx?m=135228)

     

    I've also tried restarting proxyworker, with no change to the symptoms. Very frustrating.

     

     

    emnoc
    New Member
    Nov 16, 2017 5:18 PM UTC

    Can you  do any of the following

     

     

    1: disable the ssl-inspection , wait and then re-enable

     

    or

     

    2: disable and  then re-enable the  fwpolicy-id <xxx>

     

    Does that fix the issue?

     

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT