---
sourceDocument: Yokohama API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/api-reference

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Mark service accounts as internal integration users

# Mark service accounts as internal integration users {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Allow internal integration communications to bypass the WSS authentication
requirement by marking their user accounts as internal integration users.

## Before you begin

Role required: admin

## About this task

When WS-Security is enabled, authentication is required for all SOAP requests including internal integration communications such as the MID Server, ODBC Driver, Remote Update Sets, and high availability cloning. SOAP requests for these internal integration communications cannot implement WS-Security due to technical implications. If your instance uses these SOAP interfaces, you can allow them to bypass the WS-Security authentication requirement by marking their user accounts as internal integration users.  
Note:  
Any web services other than ODBC, MID Server, Remote Update Sets, or high availability cloning must implement WS-Security headers when WS-Security is enabled.

## Procedure

1. Navigate to AllUser AdministrationUsers.
2. Select the user account for the MID Server or ODBC Driver.
3. Configure the form to add the Internal Integration User field.
4. Select the Internal Integration User check box.
5. Click Update.
**Related tasks**   

* [Enable WS-Security verification](https://www.servicenow.com/docs/py~lokLOECD6AaPO9ED5Ng "Administrators can enable Web Services Security (WSS) verification from the Web Services system properties.")  
**Related topics**   

* [WS-Security](https://www.servicenow.com/docs/Z7WcOCOBQfpudo6AaRf9Tg#c_SOAPWebService__WS-Security)

*[\>]: and then