---
title: Preparing PingAuthorize for Konnect integration
description: Prepare PingAuthorize to receive authorization requests from Kong Konnect.
component: pingauthorize
version: 10.3
page_id: pingauthorize:pingauthorize_integrations:paz_preparing_paz_konnect_integration
canonical_url: https://docs.pingidentity.com/pingauthorize/11.1/pingauthorize_integrations/paz_preparing_paz_konnect_integration.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: 2024-04-04T00:00:00Z
superseded_by: https://docs.pingidentity.com/pingauthorize/11.1/pingauthorize_integrations/paz_preparing_paz_konnect_integration.html
section_ids:
  steps: Steps
---

# Preparing PingAuthorize for Konnect integration

For Kong Konnect to use PingAuthorize as an external authorization policy runtime service, you must prepare PingAuthorize to receive authorization requests from Kong Konnect.

## Steps

1. In PingAuthorize, go to **Configuration > HTTP Servlet Extensions > Sideband API**.

2. In the **Request Context Method** list, select **State**.

3. In the **Shared Secret Header Name** field, modify the value to `CLIENT-TOKEN`.

4. Next to the **Selected** table for **Shared Secrets**, click **[icon: plus, set=fa]**to create a new shared secret.

5. In the modal, create a suitably long shared secret value and click **Save to PingAuthorize Server Cluster**.

6. At the top of the **Edit Sideband API HTTP Servlet Extension** page, click **Save**.

   ![Screen capture of the "Sideband API" screen in the administrative console with the Request Context Method set to state, the Shared Secret Header Name set to CLIENT-TOKEN, and Kong Konnect added as the selected Shared Secret.](_images/css1702914673491.png)