topic Re: Scheduled Policy not terminating existing session in General Topics

Scheduled Policy not terminating existing session

PinkPanther — Wed, 27 Nov 2019 10:33:19 GMT

Hello everybody,

I have a PA-220 and setup a rule that my children cannot access the internet after 8pm. This is working but only for new sessions. Existing sessions like TeamSpeak or BattleNet started before 8pm are still open. Can I somehow kill also existing sessions?

Thank you

Re: Scheduled Policy not terminating existing session

aamarin — Wed, 27 Nov 2019 12:53:38 GMT

This is currently a feature request.

Only new sessions will be affected by the applied security policy rule. Existing sessions are not affected by the scheduled policy.

As a workaround, to enforce the scheduled Security Policy for existing sessions, you can do either of the following:
1. Set a shorter timeout value for the application.
2. Clear the session manually.

Re: Scheduled Policy not terminating existing session

reaper — Wed, 27 Nov 2019 13:54:11 GMT

whenever you commit and have 'session rematch' enabled, active sessions will be reevaluated against the current security policy

you could script an api call for a commit job after the schedule finishes, so any 'left open' sessions are killed too

Re: Scheduled Policy not terminating existing session

PinkPanther — Thu, 28 Nov 2019 07:29:08 GMT

Thank you!

I tried this and run a scheduled task from the server with the api key. Short after it the block is working!

Re: Scheduled Policy not terminating existing session

TomYoung — Wed, 08 May 2024 14:35:41 GMT

Hi @aamarin ,

Could you share the FRID so that customers can have their SE vote for it? Not clearing active sessions defeats the purpose of the scheduled rule. The existing feature is partially implemented. It really should be a feature fix.

Thanks,

Tom

Re: Scheduled Policy not terminating existing session

aamarin — Wed, 08 May 2024 15:01:27 GMT

Hello @TomYoung,

Yes for sure, FR ID: 9854.

Thanks,

Alaa