Hello guys,
I don't know if that an expected behavior or a bug, or if it is configurable..
when the users connect via the FortiClient (we tried several versions) SSL VPN with a mobile token, they have two ways to do it:
inter the username and the password followed by the token directly after the password.
inter the username and the password hit connect, then the token display, after you enter it you can connect.
in the two ways you can connect successfully BUT, in the first method (which is wired I think in Fortinet product) the token on the FGT keeps in disable 2FA status on SSL VPN monitor, as it not applied to this user.
is that normal? or if there is a way to change it.
Thx
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Definitely a bug. Nice catch!
Hi @Moxeq ,
This is used on FGT as a backward compatibility for other third party devices that cannot prompt for the field to prompt entering token. So in this case they can provide password+otp together in the password field.
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 |
---|---|
1662 | |
1077 | |
752 | |
443 | |
220 |
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.