Description
This article describes how on firmware 6.2, users can now define and force the authentication to always take place if necessary.
On FortiOS firmware v5.2 onwards, there is an added feature of implicit fall-through where if there is firewall policies at the bottom without authentication, the user will always match the bottom policies even if there are active authentication policies at the top.
Scope
FortiGate.
Solution
By default, unauthenticated traffic is permitted to fall through to the next policy.
FortiGate only forces unauthenticated users to authenticate against the authentication policy when there are no other matching policies.
In this version, administrators can force the authentication to always take place.
To set authentication requirement, use the following command:
config user setting
set auth-on-demand <always|implicitly>
end
Always trigger firewall authentication on demand. For example:
Implicitly (default) - Implicitly trigger firewall authentication on demand.
This is the default setting and the original behavior as per version 7.0.x, 7.2.x, 7.4.x, and 7.6.
Example:
id 1: internal, (subnet1) ---> wan1, (all), service(all), has authentication.
id 2: internal, (subnet1) ---> wan1, (all), service(all), no authentication.
With auth-on-demand set to always, it will always match policy ID 1 and prompt for authentication.
This feature can be set on per-VDOM basis.
Note:
Setting auth-on-demand to 'always' will cause problems with passive authentication on FortiOS(RSSO, FSSO). In this scenario, the FortiGate will not allow authentication to fall through to different passive authentication policies.
To check whether or not auth-on-demand is responsible for FSSO authentication failing, the following diagnostics can be run on the CLI:
diag debug flow filter clear
diag debug flow filter addr <client-ip-address>
diag debug flow show ip enable
diag debug flow show function enable
diag debug console time enable
diag debug enable
diag debug flow
Test with any traffic flow that would match an FSSO policy from the <client-ip-address> device, and check if the following debug message is seen:
id=65308 trace_id=13286 func=__iprope_user_identity_check line=1894 msg="ret-stop"
If a line containing both 'func=__iprope_user_identity_check' and 'msg="ret-stop"' is visible, then auth-on-demand is preventing passive authentication from functioning as expected. To allow FSSO traffic to function as expected, set 'auth-on-demand' to 'implicitly'.
Related articles:
Technical Tip: Implicit fall-through feature for user authentication policies in 5.2
