scheduled job (execute script) possible with inactive runas account
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-23-2020 11:55 AM
Hi all,
We recently noticed that scheduled job still run when the user account selected for the runas is inactive.
I have tried finding official information from ServiceNow about this but couldn't find any. Anybode that can shed some light on this or point me to the official documentation?
Thanks
Patrick
- Labels:
-
Platform and Cloud Security

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-23-2020 12:59 PM
Hi Patrick,
Strangely even I tried figuring out but could not & thus we ensure below.
Run as: To be kept blank or System Admin
Also, we ensure that when a profile is de-activated all necessary Roles/Groups are de-associated thus ensuring that even if the Job runs it will not have that level of privilege that is required for update or perform action that may be required via scheduled job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-28-2024 05:23 PM
Hi @PatrickL ,
Apparently this is an expected behavior in the system as a lot of OOB Scheduled Jobs has the "System Administrator" set as the "Run As" user.
And a lot of the time in a during an implementation, the OOB System Administrator account needs to be de-activated due to companies' security policies. You may refer to this KB for more information