Created on
12-01-2023
09:57 AM
Edited on
01-14-2025
07:13 AM
By
Jean-Philippe_P
Description | This article describes how to resolve an authentication issue when FortiGate is authenticating through RADIUS NPS with Microsoft Entra multifactor Authentication via Azure. | ||||||||
Scope | FortiGate 7.2+ | ||||||||
Solution |
There are several instances where a system administrator may integrate FortiGate authentication through Network Policy Server (NPS) infrastructure with Microsoft Entra multifactor authentication. For instance, endpoints are able to connect to SSL VPN via RADIUS NPS then after several years or months, end-users are unable to connect to SSL VPN even though they did not make any changes.
Troubleshooting steps:
diag debug console timestamp enable diag debug res diag debug application fnbamd -1 diag debug application authd -1 diag debug enable diag test authserver radius <serverName> <scheme> <username> <password> diag debug disable
It should be possible to see that RADIUS Access-Request traffic reached the FortiGate, but the RADIUS is not sending a reply. Confirm this by analyzing the packet reaching the RADIUS server, such as by using Wireshark. For example: diagnose sniffer packet <interface_name> <'filter'> <verbose> <count> <tsformat>.
Refer to this document: Packet capture.
The script will create a self-signed certificate, associate the public key with the service principal on Microsoft Entra ID, store the certificate in the local machine certificate store, grant access to the certificate's private key to the Network User, and finally, restart the NPS service. See this article for more information.
Additional steps for systems that use the Microsoft Azure Government:
|
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 2025 Fortinet, Inc. All Rights Reserved.