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 for your environment.

  • Download the 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. For information, see Creating a 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. Complete the section titled Request context using the state field.

  • Install Apache Maven.

To begin integrating PingAuthorize with MuleSoft 4.3.0, deploy the custom MuleSoft policy. The MuleSoft policy package has a .zip archive that contains the policy files.

  1. Extract the policy files to create a project folder.
  2. Edit the pom.xml file to enter your organization's groupID.
    <?xml version="1.0" encoding="UTF-8"?>
    <project xmlns=""
        <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.

  4. Upload the PingAuthorize policy to Exchange.

The custom MuleSoft policy is now available to your APIs. For more information, see Applying the custom MuleSoft policy for PingAuthorize.