Enable WS-Security verification
Administrators can enable Web Services Security (WSS) verification from the Web Services system properties.
Before you begin
Role required: web_service_admin or admin
Procedure
-
Navigate to All > System Web Services > Properties.
-
For Require WS-Security header verification for all incoming SOAP requests, select Yes.
[Omitted image "RequireWS-Security.png"] Alt text: Require WS-Security header verification
Note: Selecting this option enables WS-Security for all inbound SOAP requests. It is not possible to enable WS-Security for only some requests.
-
Click Save.
-
Create a WS-security profile.
-
Update the user record for the Mid Server and ODBC driver to mark these users as internal integration users.
-
Download and install the latest MID Server and ODBC driver.
-
To validate SOAP request signatures, upload the remote web service's certificate as a JKS and create the web service's WSS Username Token Profile.
Note: Because ServiceNow WSS implementation does not verify the CA certificate, you do not need to upload the web service's CA certificate.
- Mark service accounts as internal integration users
Allow internal integration communications to bypass the WSS authentication requirement by marking their user accounts as internal integration users.
Parent Topic:SOAP web service
Related topics
---
title: Enable WS-Security verification
description: Administrators can enable Web Services Security \(WSS\) verification from the Web Services system properties.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/api-reference/web-services/t\_EnableWS-SecurityVerification.html
release: australia
product: Web Services
classification: web-services
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 1
breadcrumb: [SOAP web service, Inbound, Web services, API implementation, API implementation and reference]
---
# Enable WS-Security verification
Administrators can enable Web Services Security \(WSS\) verification from the Web Services system properties.
## Before you begin
Role required: web\_service\_admin or admin
## Procedure
1. Navigate to **All** > **System Web Services** > **Properties**.
2. For **Require WS-Security header verification for all incoming SOAP requests**, select **Yes**.
\[Omitted image "RequireWS-Security.png"\] Alt text: Require WS-Security header verification
**Note:** Selecting this option enables WS-Security for all inbound SOAP requests. It is not possible to enable WS-Security for only some requests.
3. Click **Save**.
4. Create a [WS-security profile](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/t_CreateANewWS-SecurityProfile.md).
5. Update the user record for the [Mid Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/t_SetupMIDServerRole.md) and [ODBC driver](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_ODBCDriver.md) to [mark these users as internal integration users](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/t_MarkSvcAcctsAsInternalIntegUsers.md).
6. Download and install the latest [MID Server](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-installation.md) and [ODBC driver](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_ODBCDriver.md).
7. To validate SOAP request signatures, upload the remote web service's certificate as a JKS and create the web service's WSS Username Token Profile.
**Note:** Because ServiceNow WSS implementation does not verify the CA certificate, you do not need to upload the web service's CA certificate.
- **[Mark service accounts as internal integration users](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/t_MarkSvcAcctsAsInternalIntegUsers.md)**
Allow internal integration communications to bypass the WSS authentication requirement by marking their user accounts as internal integration users.
**Parent Topic:**[SOAP web service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_SOAPWebService.md)
**Related topics**
[Basic authentication](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_SOAPWebService.md)
| title | Enable WS-Security verification |
| description | Administrators can enable Web Services Security \(WSS\) verification from the Web Services system properties. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/api-reference/web-services/t\_EnableWS-SecurityVerification.html |
| release | australia |
| product | Web Services |
| classification | web-services |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | SOAP web serviceInboundWeb servicesAPI implementationAPI implementation and reference |