KB2738915: Does sys_logger_configuration creation require syslog_admin or only admin?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We're implementing the Log and Allow assessment process for the Dot-Walk Scoping Security Enhancement and I'm trying to clarify the permissions required by Step 2 of KB2738915.
Specifically, Step 2 includes the"Script to create new Logger Configurations."
In our instance, a user with admin was unable to create the required sys_logger_configuration records, including when running the prescribed script in Global scope. A canCreate() check against sys_logger_configuration returned false.
During a ServiceNow Support investigation, we were advised that the missing role was syslog_admin, and Support used elevated privileges to create the required logger configuration. We were also advised that the syslog_admin requirement is not stated directly in KB2738915.
More recently, however, we've received different guidance indicating that a normal instance administrator should be able to run the Step 2 script in Global scope successfully without additional access.
I'm trying to determine the expected platform behavior rather than troubleshoot a particular instance.
For an Australia-or-later instance:
- Should a user with admin, but withoutsyslog_admin, be able to execute the KB2738915 Step 2 script and create the required sys_logger_configuration records?
- If canCreate() on sys_logger_configuration returns false for that administrator, is that expected because syslog_admin is required, or does it indicate some other configuration/access issue?
- Does running the script in the Global application scope change the applicable create ACL/role requirement?
I'm specifically interested in the expected access behavior of sys_logger_configuration for the KB2738915 procedure.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Update / Answer from ServiceNow Support
Following up with what we learned through a ServiceNow Support case, since this may save someone else some troubleshooting.
The issue was not a missing syslog_admin role.
ServiceNow Support confirmed that access to sys_logger_configuration can be blocked by OOB ACLs delivered with the Glide Logging Framework Extensions plugin. Those ACLs require the ServiceNow-internal maint role, which customers cannot normally obtain.
This explains why an administrator may be unable to create Logger Configuration records directly from the sys_logger_configuration form/table even though KB2738915 provides a scripted method for creating the same records.
There are now two relevant Problem records:
- PRB1795461: a known issue where the maint-only ACLs may only be added when the Glide Logging Framework Extensions plugin is repaired. This can explain why different instances appear to behave differently.
- PRB2136974: a newly raised defect to re-evaluate the maint-only ACLs because they prevent customer users from accessing sys_logger_configuration directly.
ServiceNow Support also tested the scripted approach documented in KB2738915 while impersonating my customer admin account and confirmed that the Logger Configuration records could be created successfully. Support subsequently rolled back those test records.
So the current practical answer appears to be:
Direct form/table creation: May be blocked by OOB maint-only ACLs.
syslog_admin: Not identified as the missing permission or cause.
KB2738915 scripted creation: Supported workaround and confirmed to work under a customer admin context
Changing/bypassing the OOB ACL: I would not recommend doing this while PRB2136974 is under review.
There is currently no ETA for PRB2136974.
This also explains an initially confusing aspect of the issue: customers may see different behavior between instances depending on whether the Glide Logging Framework Extensions plugin has been repaired and therefore whether the affected ACLs are present.
Thanks to ServiceNow Support for tracking this down. Hopefully this helps anyone else working through the Log and Allow / Logger Configuration procedure in KB2738915.