Description This article describes an issue that occurs when configuring
the RADIUS auth-type 'ms_chap_v2', which cannot be synced to the
FortiSwitch. Scope FortiOS v7.4.8 +. Solution When the FortiGate needs
to apply 802.1X authentication to the man...
Description This article describes that after the upgrade to the Feature
version, 'Use endpoints' system DNS' is no longer supported. Scope
FortiSASE. Solution The new FortiSASE instance will support IPsec VPN
instead of SSL VPN. Some SSL VPN feature...
Description This article describes how to solve the Azure CLI Login
Failure issue because the certificate verification failed. Scope
FortiSASE. Solution The end user can not access the Azure CLI with the
following error message: az loginSelect the ac...
Description This article describes that the Radius setting may be
missing after upgrading to 7v.4.8 Scope FortiGate v7.4+. Solution If a
Radius configuration is present on the FortiGate, and it needs to push
the 802.1x profile to the FortiSwitch usin...
Description This article describes the Adaptive MFA rule, which allows
bypassing the OTP by subnet range or Known devices. Scope
FortiAuthenticator v6.6.3+. Solution Starting from v6.6.3, the
FortiAuthenticator has the Adaptive MFA rule, to combines ...
https://docs.fortinet.com/document/fortigate/6.2.0/cookbook/724772/ssl-vpn-multi-realm
This is the realm config example. The purpose of the realm here is to
allow user login from different channels. You can apply with different
portals that match dif...
Does a realm + portal help in your case? If with no-domain PC, try
https://wanip/byod byod is your new realm that also matches LDAP user
but no registry key check. The new portal can help to achieve limited
access and a different IP address.