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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Create a protocol profile

# Create a protocol profile {#ariaid-title1}

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

You can create a custom HTTPS protocol profile to specify the credentials and
certificates used for outbound web services. For example, you can create a custom HTTPS
protocol profile to enable mutual authentication.

## Before you begin

* Role required: admin
* [Uploading a certificate to an instance](https://www.servicenow.com/docs/access?context=t_UploadACertificateToAnInstance&version=zurich&pubname=zurich-platform-security&ft:locale=en-US) to authenticate the client certificate of the instance.
* [Uploading a trusted server certificate](https://www.servicenow.com/docs/access?context=t_UploadATrustedServerCertificate&version=zurich&pubname=zurich-platform-security&ft:locale=en-US) to authenticate the server certificate of the web service provider.
{#t_CreateAProtocolProfile__ul_ift_ck1_3jb}

## About this task

Mutual authentication causes the web service provider and consumer to authenticate with each other before communicating. You must configure a REST or SOAP message to support mutual authentication.

* Outbound REST: Create a REST message using basic authentication.
* Outbound SOAP: Create a SOAP message using mutual authentication.

{#t_CreateAProtocolProfile__ul_o5x_dzz_hjb}  
Note:  
Mutual authentication is not available when making outbound web service calls through a MID Server.

## Procedure

1. Navigate to AllSystem SecurityProtocol Profiles.
2. Click New.
3. Fill in the fields on the form, as appropriate.  
   {#t_CreateAProtocolProfile__table_jxy_gsm_yq__entry__2}

   | Field | Description |
   |-|-|
   | Protocol | Enter a unique name to identify this HTTPS protocol, such as <kbd class="ph userinput">mauth</kbd>. The protocol name allows you to differentiate between normal HTTPS connections and HTTPS connections that use this protocol profile. The name you enter becomes the protocol name in the URL. For example, mauth://endpoint.service.com Note: * Don't include upper case letters or special characters in the protocol name. * You can't create a custom protocol with an existing protocol name such as HTTPS. {#t_CreateAProtocolProfile__ul_ilv_413_j1c} |
   | Default port | Enter the port number for connections that use this protocol. |
   | Check box | Select the client certificate the protocol uses to authenticate itself with the web service provider. The certificate must have a Type value of Java Key Store or PKCS12 Key Store. |
   [Table 1. Name of form]

   {#t_CreateAProtocolProfile__table_jxy_gsm_yq}

*[\>]: and then