Description This article describes a change in how FortiOS compares BGP
routes learned from a neighbor to those distributed from other
protocols. In firmware versions having the change, FortiOS uses original
administrative distance rather than BGP we...
Description This article describes a known issue for FortiGate-700G/701G
on v7.2.11 that can cause the link to be down after upgrading to later
firmware versions. Scope FortiGate-700G/701G, upgrading from v7.2.11
firmware to later versions. Solution ...
Description This article demonstrates FortiGate configuration for
combining client certificate authentication with RADIUS or LDAP user
authentication for IPsec VPN. Scope FortiOS v7.4.2 and later,
FortiClient v7.2. For LDAP authentication with IKEv2,...
Description This article demonstrates required settings for hosting a
SAML authentication server on the same TCP port as IKE. Scope FortiOS
v7.6.1 and later. FortiClient v7.4.1 and later. Solution In FortiOS
v7.6.1 and later, it is possible to host a...
Description This article demonstrates the use of X.509 certificates to
authenticate a FortiClient to a remote IPsec gateway, using SAML for
user authentication. Scope FortiOS v7.2.0 and later, FortiClient v7.2.4
and later. Solution Example Topology: ...
Sometimes, useful info you can only find in one place is wrong! v7.2.11
was released yesterday and v7.0.17->v7.2.11->v7.4.7 is a supported
upgrade path despite breaking the rule of thumb I just gave (v7.2.11
released 2025-02-12, v7.4.7 released 2025-...
It's not because v7.0.17 was new, upgrade from chronologically later
(v7.0.17) releases to chronologically earlier (v7.2.10) releases is not
supported. That's because those upgrade steps are not QA-tested. Upgrade
v7.0.17->v7.2.10 or earlier should b...
Not monitoring this post, but dropping "word of TAC" here in since I'm
seeing it's unclear.This February 28 2025 FortiGate Cloud change applies
for devices without a FortiGate Cloud subscription, either per-device or
at the account level. It is diffe...
Hi Toshi,I can believe it. The Change Log has since been updated again
and CVE-2024-47575 is referenced in Resolved Issues.As you've noticed,
not all Known or Resolved Issues appear immediately in Release Notes.
Some never appear. For urgent releases...