I found a cookbook article for 5.2 but that doesn't hold for 6.03.
We are trying to transition from a Squid based Man in the Middle filter system to the Fortigate. We do not want to install the fortigate cert on all the machines, since we already have one installed and working. Much rather make that one the signer on the fortigate.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
You can use internal certificate authority, on FGT you need to generate CSR and then issue certificate (template „Subordinate Certification Authority”)
I have the Certificate installed and being used for SSL Deep Packet Inspection and it is working great there. The explicit proxy does not use this one and I cannot seem to locate how, in 6.03, to point it to this cert.
In the proxy policy you have Security Profiles, as with Firewall Policies. Set the profile with the correct cert
What do you see in the UTM logs? You can also enable logging all sessions just for the troubleshooting
So I ended up opening a support ticket for this issue.
The engineer noticed something that should not be possible. In the Proxy Policy the service was not set. I say that this is not possible, because that is a required field. When the engineer was changing the Logging options, it error'd on that field until it was set.
So all is functioning. Still not sure why I was getting the Fortigate's self signed cert, but problem solved.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1660 | |
1077 | |
752 | |
443 | |
220 |
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.
Copyright 2024 Fortinet, Inc. All Rights Reserved.