Hello everyone,
I recently discovered that the FortiAuthenticator supports a proxy authentication mode for remote RADIUS servers:
FortiAuthenticator Documentation
However, the FortiGate does not seem to offer a similar option:
If you want to set up remote Dial-Up IPsec VPN tunnels using EAP-TLS authentication via Microsoft NPS (RADIUS), it seems you would need to purchase a FortiAuthenticator solely to forward the requests to the remote RADIUS server.
Will FortiGate ever introduce a proxy mode for authentication via remote RADIUS servers?
Solved! Go to Solution.
The FortiGate is simply instructed to:
EAP methods are not configured on the FortiGate, this is negotiated between the supplicant (endpoint) and the EAP server through the "EAP tunnel". The correct place to enforce acceptable EAP methods is thus on the EAP/RADIUS server.
Btw, AFAIK FortiClient does not support EAP-TLS. When configured to send a user certificate, cert-based auth is performed (non-EAP).
As for documentation, you can use this as a starting point:
I haven't tested it personally, so I cannot vouch for it to be 100% correct, but it sufficiently demonstrates how the config should look. Notice how there's no step where you configure which EAP method is to be used in the FGT's config.
The main challenge right now is the FortiClient. It seems we’ll need to switch to a different VPN client, as the FortiClient isn’t fully optimized for VPN functionality.
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 |
---|---|
1740 | |
1108 | |
752 | |
447 | |
240 |
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.