 Re: Timeout configuration
Imagine you just edited twenty rules and you pick up an incoming phone call which is longer than your session timeout. You would be logged out and all changes would be lost. Or even worse, you deleted a object which had a VPN certificate installed, the certificate got deleted and the session timeout logs you out. The deleted object would still be there after your next login while the VPN certificate would not. Check Point knew that a session timeout could lead to reference errors in the objects database due to unsaved states while logging someout out this way. Also a lot of other unwanted side-affects could appear. In an IT-security environment you want stable processes and states.
Better create readonly and readwrite admin profiles and use these instead of looking for a session timeout to log someone out that is logged in for hours or days by a session timeout. Multiple admins may be logged in at the same time in readonly mode to check SmartView Monitor or SmartView Tracker for a longer time period. If someone needs to edit the security policy or something, he might log in with readwrite permission and logout afterwards.  | 
Timeout configuration 
2008-05-14 
Linear Mode
