---
title: Deploying the custom MuleSoft policy for PingAuthorize
description: Deploy the custom MuleSoft policy to make it available to your integrated APIs.
component: pingauthorize
version: 11.0
page_id: pingauthorize:pingauthorize_integrations:paz_deploy_mulesoft_policy_paz
canonical_url: https://docs.pingidentity.com/pingauthorize/11.0/pingauthorize_integrations/paz_deploy_mulesoft_policy_paz.html
revdate: July 16, 2025
section_ids:
  before-you-begin: Before you begin
  steps: Steps
  example: Example:
  result: Result
---

# Deploying the custom MuleSoft policy for PingAuthorize

Deploy the custom MuleSoft policy to make it available to your integrated APIs.

## Before you begin

You must:

* Have the correct MuleSoft version.

  The custom policy supports MuleSoft 4.3.0. If you are using any other version, contact Ping Identity support.

* Install and configure PingAuthorize software.

  See the [PingAuthorize installation information](../installing_and_uninstalling_pingauthorize/paz_install_pingauthorize.html) for your environment.

* Download the [MuleSoft integration kit for PingAuthorize](https://marketplace.pingone.com/item/mulesoft-integration-kit-for-pingauthorize), which contains the custom MuleSoft policy.

* Create a sideband adapter shared secret.

  Sideband adapters like the custom MuleSoft policy use a shared secret header to authorize against PingAuthorize. Learn more in [Creating a shared secret](../pingauthorize_server_administration_guide/paz_authn_sideband_api.html#create_sideband_shared_secret).

  |   |                                                                                             |
  | - | ------------------------------------------------------------------------------------------- |
  |   | Make sure you record the shared secret value. You need it to configure the MuleSoft policy. |

* Configure the sideband adapter request context.

  For more information, see [Request context configuration](../pingauthorize_server_administration_guide/paz_request_context_config.html). Complete the section titled Request context using the state field.

* Install Apache Maven.

## Steps

1. Extract the policy files to create a project folder.

2. Edit the `pom.xml` file to enter your organization's `groupID`.

   ### Example:

   ```xml
   <?xml version="1.0" encoding="UTF-8"?>
   <project xmlns="http://maven.apache.org/POM/4.0.0"
            xmlns:xsi="http://www.w3.org/2001/XMLSchemainstance"
            xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
       <modelVersion>4.0.0</modelVersion>

        <groupId>aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee</groupId>

       <artifactId>PingAuthorize</artifactId>
       <version>0.4.0</version>
       <name>PingAuthorize</name>
       <description>PingAuthorize sideband policy for Mule 4.X APIs deployed on Mule Cloudhub from Ping Identity</description>
   ```

3. From the command line in your project folder, run the following command to package the PingAuthorize policy and create a deployable `.jar` file. `> mvn clean install`

   |   |                                                                                                                                                                                                                                                                                                               |
   | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | You must have a MuleSoft Enterprise Repository license to compile the policy. For more information, see *Configure Maven to Access MuleSoft Enterprise Repository* in [Maven Reference](https://docs.mulesoft.com/mule-runtime/4.3/maven-reference#configure-maven-to-access-mulesoft-enterprise-repository). |

4. Upload the PingAuthorize policy to **Exchange**.

   For more information, see [Deploying a Policy Created Using the Maven Archetype](https://docs.mulesoft.com/api-manager/2.x/custom-policy-uploading-to-exchange).

## Result

The custom MuleSoft policy is now available to your APIs. For more information, see [Applying the custom MuleSoft policy for PingAuthorize](paz_apply_mulesoft_policy_paz.html).