Property reference

`glide.security.disable_ui_pages_sysparm_client_script`

The glide.security.disable_ui_pages_sysparm_client_script property controls whether client scripts passed via URL parameters are evaluated in UI pages. Admins should disable this property temporarily if their implementation relies on such scripts, but it should not be left disabled long-term.

Default: Not stated
Type: Not stated
Application: Not stated

Key questions about this property

The answers below summarize the purpose, scope, default effect, and review scenarios for this property.

What does it do?	This property prevents the evaluation of client scripts included in URL parameters for UI pages, enhancing security by avoiding potential script injection.
What area does it affect?	UI Pages
What does the default mean?	No default value is stated in the ServiceNow documentation.
When should you review it?	Review this property when modifying UI page implementations that utilize URL parameters for client scripts.

Property record

Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.

Property name	`glide.security.disable_ui_pages_sysparm_client_script`
Type	Not stated
Application	Not stated
Default value	Not stated
Description	Not stated

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs View supporting context

Context preview Snippet 1

... client scripts in UI pages. The system no longer evaluates scripts that are passed by URL parameter. If your implementation depends on this behavior, you can add the system property [glide.security.disable_ui_pages_sysparm_client_script] and set it to false to temporarily allow the evaluation of URL parameters passing scripts in UI pages. Use access controls on UI pages See access controls directly from the ...

Brazil docs View supporting context

Context preview Snippet 2

... Type: true | false • Default value: false • Location: Add the property to the System Property [sys_properties] table. • Instance Security Hardening Settings: Performance monitoring (ACL) (instance security hardening) glide.security.disable_ui_pages_sysparm_client_script The system does not evaluate client scripts that are passed in URL parameters in UI pages. If you use URL parameters to load client scripts, you can add and disable ...

More in `glide.security`

Other properties in the same namespace.

glide.security.csrf.strict.validation.mode This property determines whether strict validation of CSRF tokens is enforced, blocking requests with mismatch glide.security.csrf_previous.allow This property allows expired secure tokens to be used for request validation, impacting CSRF protection mechan glide.security.csrf_previous.time_limit This property defines the duration a secure token remains valid, expiring when the user session ends unless sp glide.security.diag_txns_acl This property allows only admin users or users from specified IP addresses to access the stats.do, threads.do, glide.security.empty_acl.popup_window.enabled This property enables a popup window alerting users when an empty ACL is encountered, enhancing security aware glide.security.empty_acl_bounce This property triggers a fix for empty ACLs by adding a script to their configuration, ensuring they are prope glide.security.enable.deny_empty_or_invalid_acl_validation This property enforces validation checks on ACLs, ensuring they are properly configured and not left empty or glide.security.enable_archive_table_acls This property enables or disables the enforcement of active 'read' ACLs on archive tables, defaulting to true

All 62 properties in glide.security →