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 enforces the requirement for WS-Security headers in all incoming SOAP requests, improving security for web service interactions. |
| What area does it affect? |
SOAP web services |
| What does the default mean? |
The default value is "false", which means this behavior is disabled by default. |
| When should you review it? |
Review this property when enhancing security measures for SOAP integrations or during security audits. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.soap.require_ws_security |
| Sys ID |
bbabaf03ff3200007fe1fe51c17f9d4c |
| Type |
boolean |
| Application |
Global |
| Default value |
false |
| Description |
Require WS-Security header verification for all incoming SOAP requests |
| Updated |
2024-05-25 04:35:43 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... to query the database must have the soap_query role if the instance uses the glide.soap.strict_security high security setting. Warning: Do not enable WS-Security for all SOAP requests by setting the glide.soap.require_ws_security system property. It is incompatible with the ODBC driver. Enabling this setting blocks both ODBC driver and MID Server connections. Instead, use basic authentication. Target Table ACLs The user you ...
Context preview
Snippet 2
... for SOAP requests • New remediation: Ensure the Glide Property glide.basicauth.required.soap exists and is set to the value true. Alternatively, configure the instance for WS Security by setting the property glide.soap.require_ws_security to true and following the product documentation to configure WS Security Profiles. If the property does not appear in the sys_properties table, add a new record. • Old remediation: Ensure ...
Related properties