FAQ--- The wireless PC is forced to reauthenticate by the portal server after a period of inactivity

Publication Date:  2016-10-31 Views:  393 Downloads:  0
Issue Description

Portal authentication is implemented from the Agile Controller for a wireless network but the end users are forced to reauthenticate  after a period of time from the first authentication.


The Agile controller portal server provides a session timeout interval for mobile users (smartphones and tables)   which is used as a mechanism of limiting the time a user can access the wireless resources.   In the case of wireless PCs this mechanism is disabled by default and instead the web browser periodically sends a heartbeat message to the portal server  (you can modify the heartbeat interval in Global Parameters )  in order to check the connectivity to the server. In the situation where the authentication page is closed on the wireless PC, the web browser cannot respond to the heartbeat message and the user may be forced to go offline after a period of time . The heartbeat session timeout interval is 10 minutes by default for PCs, hence if the the portal page is closed on a PC, the user will be disconnected after 10 minutes of inactivity and would not be able to access the resources any more afterwards. 


To solve the problem where PCs are disconnected after the authentication page is closed, we can either enable the Wireless PC compatibility in the “ Configure Web Timeout Interval for Wireless Terminals” tab in order to use the same session timeout mechansim for PCs  as for the mobile users or we can extend the heartbeat session interval in the “Configure Heartbeat Interval Parameters “ from 10 minutes to a larger value in order to increase the time the server can wait for a heartbeat message from the PCs.