Kill a user session if idletime superior to X
Hey. Version 9.32. There is an integration user that for some reason gets stuck and creates a lot of sessions. Most of them idle. What is the best way to:
- if the user is X and idletime is X, kill user session?
Take a look at the thread bellow and se if it works for you:
You can also instruct the developer to use keep alive to not overload SM with multiple logins and to execute the logoff at the end.
You can also adjust the parameter https://docs.microfocus.com/SM/9.41/Codeless/Content/parameters/reference/parameter_webservicestimeout.htm
If you feel this was helpful please click the KUDOS! thumb below!
In the operator table there is a field called "idletime". The form didn't have the field so I placed a text field with the input "idletime". Added 5 minutes and saved. This didn't work. My issue is that there are intergration users that get their sessions idle for more than 20 minutes.
The inactivity timer setup works on a general level. The goal is to place this rule on 1 user only.
You may want to consider limiting sessions for users and updating the idle time. If user is stuck and cannot wait for idle time to kill session on its own, you can manually kill there sessions from "System Status".
--Base System Configuration
----System Information Record (Within Login Info tab, update the max logins per user.)
Setting Idle Time:
----Start Inactivity Timer (Note, adding an account to the "Do Not Terminate" list will not terminate operator session. Used mainly for admins.)
I have workaround for you:
Make new schedule record activating every X minutes and call JS from it:
Add SL KillUser and function in it
var rteReturnValue = new SCDatum();
var argNames = new SCDatum();
var argVals = new SCDatum();
var arrNames = new Array();
var arrValues = new Array();
var rc = system.functions.rtecall("callrad",
A different angle to the problem.
Not sure what sort of integration you are doing but for web services, it's best to dedicated a servlet specifically for it. The servlet will be hidden from load balancer via debugnode:1 and it will have reduced timeout specifically for high volume short duration transactions like web services which are different from user transaction via load balancer which are of long duration..