Skip to main content

Active sessions: restrict concurrent users for same user and specify session timeout

 https://docs.servicenow.com/bundle/paris-platform-administration/page/integrate/authentication/task/limit-concurrent-sessions-plugin.html


https://docs.servicenow.com/bundle/paris-platform-administration/page/integrate/authentication/concept/limit-concurrent-sessions.html


https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/security/reference/session-activity-timeout.html


after you have installed the plugin Limit Concurrent Sessions plugin (com.glide.limit.concurrent.sessions)  

these properties need to be set to true: glide.authenticate.limit.concurrent.interactive.sessions
and to the glide.ui.session_timeout value desired (default is 60 mins)

you may wish to run the following fix script and code this business rule also to default the setting:

BUSINESS RULE: default limit_concurrent_sessions to true when creating a new user (exclude integration users if you wish) - before insert and set condition to 'u_service_account=false' or similar

(function executeRule(current, previous /*null when async*/) { //-- see STRY0010717 current.limit_concurrent_sessions=true; })(current, previous);




FIX SCRIPT: bulk update existing users

var grUsers = new GlideRecord('sys_user'); grUsers.addQuery('u_service_account', 'false'); grUsers.addQuery('limit_concurrent_sessions', 'false'); //grUsers.query(); //gs.print(grUsers.getRowCount()); grUsers.setValue('limit_concurrent_sessions', 'true'); grUsers.updateMultiple();


Comments

Popular posts from this blog

ServiceNow timeout settings for virtual agent chat

  After connecting to live agent User is connected to live agent and not responding to live agent chat or distracted. The below properties controls the timeout settings, the OOB settings for reminder is [180 sec] and for cancelling the chat is [360 sec]. The job is default configured to 2 min so I believe no tweaking is required here.  Property -   com.glide.cs.idle_chat_reminder_timeout                  com.glide.cs.idle_chat_cancel_timeout Scheduled job   - Idle Chat Timer Task   https://community.servicenow.com/community?id=community_article&sys_id=1453b03bdbaad0109e691ea668961929   (ServiceNow ) 

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){...