Description |
This article describes why RADIUS is configured with PAP but IPsec dial-up authentication is still sent using MS-CHAP v2. |
Scope |
FortiGate. |
Solution |
A RADIUS server is configured using PAP as the authentication type:
show config user radius edit "Duo-RADIUS" set server "172.16.2.1" set radius-port 11812 set auth-type pap next end
However, when running fnbamd debug for IPsec VPN, it is possible to see that the authentication type is sent using MS-CHAPP v2 instead:
[1906] handle_req-Rcvd auth req 963834393 for henry@test.com in FortiClient IPSEC Users opt=00000000 prot=5 This happens because the xauth type under IPsec configuration is set to 'auto'. It is possible to force the device to use PAP with the following commands:
config vpn ipsec phase1-interface edit <Tunnel_name> set xauthtype pap Note: For the GUI, convert the tunnel to 'custom'. The 'Type' section will then be possible to change in the XAUTH tab.
After that, run the fnbamd debug again. Upon trying to authenticate, PAP will be used accordingly:
[1802] fnbamd_radius_auth_validate_pkt-RADIUS resp code 3 |
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
This post is very helpful!!