Fortigate SSL VPN Timeout Issue with Approve/Biometrics
Last Modified: 2026-01-14
Article Number
Applies To
Issue
Users are unable to log in to the SSL VPN using Approve or biometric authentication from CAS.
Resolution
- Log in to the Fortigate CLI.
- Select the correct VDOM based on customer configuration.
- Configure the remoteauthtimeout parameter:
FEIRDUFG01$ config sys global
FEIRDUFG01(global)$ set remoteauthtimeout 60
FEIRDUFG01(global)$ end
Notes
About remoteauthtimeout
- This is a global parameter for LDAP, RADIUS, and other authentication servers.
- It defines the maximum time (in seconds) allowed for a valid token code to be entered before the connection closes.
- Default value: 5 seconds.
- Important: Changing this value affects all remote authentication servers (RADIUS, LDAP, TACACS+).
Related Articles
Troubleshooting an update issue with an RSA Authentication Manager 8.x Web Tier deployment 366Number of Views “An issue with handling encryption was encountered" with IBM JDK 1.8.0_281 and later in RSA Identity Governance & Lifecycle 462Number of Views AFX Server remains in a 'Not running' State with 'An issue with handling encryption was encountered' error on startup in R… 502Number of Views Issue with Identity Confidence-Based Access Policies in the IDR SSO Portal 18Number of Views Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle 1.33KNumber of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?