Created on
‎07-31-2023
01:29 AM
Edited on
‎11-27-2025
01:49 AM
By
Jean-Philippe_P
| Description |
This article describes how to solve incorrect RADIUS authentication when a user is connecting to the SSL VPN. |
| Scope | FortiGate, FortiProxy. |
| Solution |
This article describes how the option 'Include in every user group' in the RADIUS server configuration on FortiGate might lead to incorrect RADIUS authentication in SSL VPN connections.
The option 'Include in every user group' should be enabled on the RADIUS server in special cases where every SSL VPN user must be matched with all locally configured RADIUS groups on FortiGate itself.
config user radius next
Here is a config example that shows when a user is connected to the SSL VPN, is authenticated as a member of an incorrect SSLVPN group according to the config on FortiGate:
config user radius edit "radius.server" set server "10.125.5.129" set secret <secret_key> set all-usergroup enable <--------- set nas-ip 10.125.0.203 next end
config user local edit "zilan" set type radius set radius-server "radius.server" next end
config user group edit "radius.users-1" <----- This RADIUS group has only one local radius user as a member. set member "zilan" next end
config user group edit "radius.users-2" set member "radius.server" next end
config vpn ssl settings set servercert "Fortinet_Factory" set tunnel-ip-pools "SSLVPN_TUNNEL_ADDR1" set tunnel-ipv6-pools "SSLVPN_TUNNEL_IPv6_ADDR1" set source-interface "wan1" set source-address "all" set source-address6 "all" set default-portal "full-access" config authentication-rule edit 1 set groups "radius.users-1" <------------- set portal "tunnel-access" next end end
config firewall policy edit 4 set name "sslvpn-out" set srcintf "ssl.root" set dstintf "wan1" set action accept set srcaddr "all" set dstaddr "all" set schedule "always" set service "ALL" set nat enable set groups "radius.users-1""radius.users-2" <------------- next end
Run the following debugging commands to see the authentication result after the user is connected to the SSL VPN:
diagnose debug disable
The user 'sara' is expected to be authenticated only as a member of the radius group "radius.users-2", but debug output shows the user 'sara' is authenticated as a member of radius group 'radius.users-1' as well which is incorrect as per above config since this group 'radius.users-1' has only one local radius user member named 'zilan':
Note: As per FortiOS design, both enabled radius groups on the SSL VPN firewall policy will be checked by FortiGate.
local auth: 0, dn match: 0 len=2141 Authenticated groups (2) by FNBAM with auth_type (2): grp_info=[QHpHzE],rmt_grp_info=[fFGbPD] csrf_token=[<token>],idx=0,auth=2,sid=6d59d1f5,login=1690770404,access=1690770404,saml_logout_url=no,pip=no, grp_info=[QHpHzE],rmt_grp_info=[fFGbPD]
get vpn ssl monitor
SSL-VPN sessions:
To resolve this issue option 'Include in every user group' must be disabled in the RADIUS server settings on FortiGate as follows:
config user radius |
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.