Property reference

`glide.soap.strict_security`

Enforces security-manager checks for incoming SOAP requests, including table and field access and required user roles. With the default value of true, SOAP users need appropriate access and web service roles to make requests.

Default: true
Type: boolean
Application: Global
Category: Integrations, APIs & Web Services

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 requires incoming SOAP requests to be validated through the security manager for access to tables and fields, ensuring only authorized users can interact with the web service.
What area does it affect?	SOAP web services
What does the default mean?	The default value is "true", which means this behavior is enabled by default.
When should you review it?	Review this property when configuring SOAP integrations or assessing security protocols.

Out of the box property record

Raw metadata from the property record.

Property name	`glide.soap.strict_security`
Sys ID	`33ad80d80a0a0b500050ffc63d3935f6`
Type	boolean
Application	Global
Default value	`true`
Description	Enforce strict security on incoming SOAP requests. Checking this requires incoming SOAP requests to go through the security manager for table and field access, as well as checking SOAP users for the correct roles for using the web service.
Updated	2024-05-25 03:58:22

Sources

Official references and nearby text excerpts where this property appears.

Brazil docs Create a WS-Security profile ↗

Context preview Snippet 1

... then the instance treats all web services operations as being done by the system administrator. Make sure the user you select has appropriate SOAP privileges if you are using the glide.soap.strict_security high security setting. This field is only visible when the type is X509. Order Enter the order in which the instance checks security profiles. The instance checks all security profiles ...

Brazil docs Enforce SOAP request strict security ↗

Context preview Snippet 2

... to XML export data, when combined with misconfigured guest user role, poses a significant risk of unauthorized data exposure. Enforce SOAP request strict security • Description ◦(Old‎ <blank> ◦(New‎ If "glide.soap.strict_security" is not set to the recommended value of "true", then users do not need a SOAP role to make requests of non-public pages when the high security or web service ...

Additional source link Another external reference for this property

Open reference

More in `glide.soap`

Other properties in the same namespace.

glide.soap.request_processing_timeout This property defines the timeout duration for SOAP request processing, defaulting to 60 seconds, which can im glide.soap.request_processing_timeout.odbc This property defines the timeout period in seconds for the ODBC driver during SOAP request processing, impact glide.soap.require_content_type_xml It enforces validation of the Content-Type header for SOAP requests, ensuring that only requests with 'text/xm glide.soap.require_ws_security This property enforces the requirement for WS-Security headers in all incoming SOAP requests, improving securi glide.soap.allow_null_numeric_output When enabled, returns an empty XML element for numeric fields with no value in SOAP responses; when disabled, glide.soap.default_security_policy This property determines the security policy applied to SOAP web services when WS-Security is enforced, ensuri glide.soap.enforce_field_acls This property enforces field-level ACLs for SOAP API interactions, restricting access based on user permission glide.soap.import_set_insert_serialized When true, processes simultaneous web service inserts into an import set table one at a time across nodes; whe

All 12 properties in glide.soap →