just tried to enable https scanning with the new explicit proxy on a fortigate 110C,310B and 80C but https doesn' t get decrypted.
Has anyone the same behavior?
To check it:
-Enable explicit proxy on a internal interface
-create a " protocol profile" with deep scanning enabled
-create " av profile" with av inside http and https enabled
-create a rule from src interface " web-proxy" to " external interface"
check utm radio button and select created " av profile" and " protocol profile"
Last week I spoke with fortinet after submiting a bug report and the HTTPS feature for web proxy is not working and they know about it. It is scheduled to be fixed in release 4.3.
Also the safe search engine is broken as well and it is a bug that fortinet is working on fixing in the current release.
Also I noticed that the users that authenicate to the web proxy do not show up on the monitored user list. Fortinet has not addressed this issue yet.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.