--- title: Applying the custom MuleSoft policy for PingAuthorize description: Apply the deployed custom MuleSoft policy to an API so you can connect it to PingAuthorize for external authorization decisions. component: pingauthorize version: 10.2 page_id: pingauthorize:pingauthorize_integrations:paz_apply_mulesoft_policy_paz canonical_url: https://docs.pingidentity.com/pingauthorize/11.1/pingauthorize_integrations/paz_apply_mulesoft_policy_paz.html llms_txt: https://docs.pingidentity.com/pingauthorize/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-04-01T00:00:00Z superseded_by: https://docs.pingidentity.com/pingauthorize/11.1/pingauthorize_integrations/paz_apply_mulesoft_policy_paz.html section_ids: steps: Steps result: Result: next-steps: Next steps --- # Applying the custom MuleSoft policy for PingAuthorize You must apply the deployed custom MuleSoft policy to use MuleSoft as an API gateway with PingAuthorize. The PingAuthorize policy supports HTTP APIs configured with the `Endpoint with proxy` or `Basic Endpoint` options. ## Steps 1. Sign on to your MuleSoft Anypoint account. 2. Go to the API manager, expand the API to which you want to attach the PingAuthorize policy, and click **Version**. ![Screen capture of the Manage API screen in the MuleSoft API Manager with a callout highlighting the Version value](_images/bhz1626284943995.png) 3. In the left navigation pane, click **Policies**. The **Policies** page supports applying the PingAuthorize policy to the API. ![Screen capture of the PingAuthorizeAPI v1 - Settings window under the Policies tab (highlighted) in the MuleSoft API Manager](_images/ewo1626284987474.png) 4. Click **Apply New Policy**. ![Screen capture of the PingAuthorizeAPI v1 Policies window under the Policies tab with the Apply New Policy button highlighted in lower center of the screen](_images/pyz1626285305789.png) ### Result: The **Select Policy** window opens. 5. In the **Select Policy** window, select the PingAuthorize policy and current version. Click **Configure Policy**. ![Screen capture of the Select Policy page with the PingAuthorize policy highlighted](_images/ame1626285146143.png) 6. On the **Apply Policy** page, enter the following values: 1. In the **PAZ Token** field, enter the sideband adapter shared secret generated as part of the prerequisites in [Deploying the custom MuleSoft policy for PingAuthorize](paz_deploy_mulesoft_policy_paz.html). 2. In the **PAZ Host** field, enter the PingAuthorize host and port. | | | | - | ------------------------------------------------------------- | | | Do not include the connection scheme (http\:// or https\://). | 3. Select the **Enable SSL** checkbox for a secure HTTPS connection between MuleSoft and PingAuthorize. 4. Select the **Allow self-signed certificate** checkbox to enable MuleSoft to accept a self-signed certificate from PingAuthorize. Learn more about configuring PingAuthorize to use trusted certificates in [Importing signed and trusted certificates](../pingauthorize_server_administration_guide/paz_import_signed_certs.html). 5. Select an access token type: Choose from: * Use Authorization Header: Indicates that the authorization header of an incoming request should be passed to PingAuthorize and used to authorize the client. * Use hard-coded parsed access token: Allows configuration of an access token that will be used for every request. Use this only for testing purposes. * Use parsed access token: Allows configuration of a DataWeave expression for retrieving a parsed access token from the Mule message. When you use MuleSoft's OAuth 2.0 Token Enforcement policies to obtain a parsed access token, use the expression `#[authentication.properties.userProperties]`. Learn more in [DataWeave Language](https://docs.mulesoft.com/mule-runtime/4.3/dataweave). 6. (Optional) Configure the **Connection Timeout** and **Read Timeout**. Timeouts govern the behavior of the API gateway when it cannot connect to PingAuthorize or the response from PingAuthorize is delayed. | Timeout parameter | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connection Timeout | Governs the time the API gateway waits to establish a connection with PingAuthorize, following which it sends the client request to the backend server. | | Read Timeout | Governs the time the API Gateway waits for PingAuthorize's response before sending the request to the backend server. | | | | | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | The default value is 5000 milliseconds (5 seconds). It's good practice to configure a small value to limit the delay in case PingAuthorize isn't reachable or is unresponsive. | 7. (Optional) Select the **Enable debug logging** checkbox to see requests sent to PingAuthorize Server along with responses. 8. (Optional) Configure **Methods & Resource Conditions**. Learn more in [Resource-Level Policies](https://docs.mulesoft.com/api-manager/2.x/policies-policy-level) in the MuleSoft documentation. ![Screen capture of the Apply PingAuthorize policy page with fields completed as directed in steps 6a - 6h and in the Apply button in the lower right](_images/fej1626285074831.png) ## Next steps If there are any changes to PingAuthorize endpoints, repeat the process explained in step 6 and re-deploy the configuration.