bodminman Posted February 28, 2022 Posted February 28, 2022 (edited) Hi there, our Smoothwall went live last week and I'm under the cosh to get a particular issue ironed out. The boarders, who started to arrive back yesterday are connecting to the SSL login page fine, but the sessions are set to timeout after 20 minutes. This makes it impossible for them to watch films and Zoom their parents etc without disruptions. What can be done about this? Many thanks Edited February 28, 2022 by bodminman
icemonkey Posted February 28, 2022 Posted February 28, 2022 If they keep the SSL login page open, the connection will remain authenticated. If they close it, the Login Timeout value applies. The value can be adjusted under Services -> Authentication -> Settings -> Login Timeout but you'll have to decide if a longer timeout is acceptable from safeguarding/security perspectives. Other options are: - Use timeslots to allow access to sites between certain hours (or outside of learning hours) - Look at other authentication options such as RADIUS 1
bodminman Posted February 28, 2022 Author Posted February 28, 2022 If they keep the SSL login page open, the connection will remain authenticated. If they close it, the Login Timeout value applies. The value can be adjusted under Services -> Authentication -> Settings -> Login Timeout but you'll have to decide if a longer timeout is acceptable from safeguarding/security perspectives. Other options are: - Use timeslots to allow access to sites between certain hours (or outside of learning hours) - Look at other authentication options such as RADIUS So with ours setup as below, would you suggest changing it to redirect to SSL login page with background tab? I will be looking at the Radius side of things over Easter but need a quick fix or better fit right now.
ibpalle Posted March 7, 2022 Posted March 7, 2022 You can increase the login timeout for now in services - authentication - settings. If this is for BYOD devices, then set a long DHCP lease time and set the timeout to be high. The reason for the high lease time in DHCP is that the login will persist so if another device gets the same IP before the login expires, they will be browsing as the previous user.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now