Secure A2A endpoints with OpenID Connect and Okta

This is a Konnect tutorial and requires a Konnect personal access token.

1. Create a new personal access token by opening the Konnect PAT page and selecting Generate Token.

2. Export your token to an environment variable:

    export KONNECT_TOKEN='YOUR_KONNECT_PAT'
   

   Copied!

3. Run the quickstart script to automatically provision a Control Plane and Data Plane, and configure your environment:

    curl -Ls https://get.konghq.com/quickstart | bash -s -- -k $KONNECT_TOKEN --deck-output
   

   Copied!

   This sets up a Konnect Control Plane named quickstart, provisions a local Data Plane, and prints out the following environment variable exports:

    export DECK_KONNECT_TOKEN=$KONNECT_TOKEN
    export DECK_KONNECT_CONTROL_PLANE_NAME=quickstart
    export KONNECT_CONTROL_PLANE_URL=https://us.api.konghq.com
    export KONNECT_PROXY_URL='http://localhost:8000'
   

   Copied!

   Copy and paste these into your terminal to configure your session.

This tutorial requires Kong Gateway Enterprise. If you don’t have Kong Gateway set up yet, you can use the quickstart script with an enterprise license to get an instance of Kong Gateway running almost instantly.

1. Export your license to an environment variable:

    export KONG_LICENSE_DATA='LICENSE-CONTENTS-GO-HERE'
   

   Copied!

2. Run the quickstart script:

   curl -Ls https://get.konghq.com/quickstart | bash -s -- -e KONG_LICENSE_DATA 
   

   Copied!

   Once Kong Gateway is ready, you will see the following message:

    Kong Gateway Ready
   

decK is a CLI tool for managing Kong Gateway declaratively with state files. To complete this tutorial, install decK version 1.43 or later.

This guide uses deck gateway apply, which directly applies entity configuration to your Gateway instance. We recommend upgrading your decK installation to take advantage of this tool.

You can check your current decK version with deck version.

For this tutorial, you’ll need Kong Gateway entities, like Gateway Services and Routes, pre-configured. These entities are essential for Kong Gateway to function but installing them isn’t the focus of this guide. Follow these steps to pre-configure them:

1. Run the following command:

   echo '
   _format_version: "3.0"
   services:
     - name: a2a-currency-agent
       url: http://host.docker.internal:10000
   routes:
     - name: a2a-route
       paths:
       - "/a2a"
       strip_path: true
       service:
         name: a2a-currency-agent
       protocols:
       - http
       - https
   ' | deck gateway apply -
   

   Copied!

To learn more about entities, you can read our entities documentation.

This tutorial uses OpenAI:

1. Create an OpenAI account.
2. Get an API key.

3. Create a decK variable with the API key:

   export DECK_OPENAI_API_KEY='YOUR OPENAI API KEY'
   

   Copied!

You need a running A2A-compliant agent. This guide uses a sample currency conversion agent from the A2A project.

Create a docker-compose.yaml file:

cat <<'EOF' > docker-compose.yaml
services:
  a2a-agent:
    container_name: a2a-currency-agent
    build:
      context: .
      dockerfile_inline: |
        FROM python:3.12-slim
        WORKDIR /app
        RUN pip install uv && apt-get update && apt-get install -y git
        RUN git clone --depth 1 https://github.com/a2aproject/a2a-samples.git /tmp/a2a && \
            cp -r /tmp/a2a/samples/python/agents/langgraph/* . && \
            rm -rf /tmp/a2a
        ENV UV_COMPILE_BYTECODE=1 UV_LINK_MODE=copy
        RUN uv sync --frozen --no-dev
        EXPOSE 10000
        CMD ["uv", "run", "app", "--host", "0.0.0.0"]
    environment:
      - model_source=openai
      - API_KEY=${DECK_OPENAI_API_KEY}
      - TOOL_LLM_URL=https://api.openai.com/v1
      - TOOL_LLM_NAME=gpt-5.1
    ports:
      - "10000:10000"
EOF

Export your OpenAI API key and start the agent:

export DECK_OPENAI_API_KEY='your-openai-key'
docker compose up --build -d

The agent listens on port 10000 and uses the A2A JSON-RPC protocol to handle currency conversion queries. In this guide, the gateway service points to host.docker.internal:10000 instead of the container name because Kong Gateway runs in its own container with a separate DNS resolver.

You need an Okta admin account with a developer organization.

Add a custom scope

1. Go to Security > API > Authorization Servers.
2. Click default.
3. Go to the Scopes tab.
4. Click Add Scope.
5. Name: api:access
6. Display phrase: Access protected APIs
7. Check Set as a default scope.
8. Click Create.

Add an access policy

1. In the same default authorization server, go to the Access Policies tab.
2. Click Add Policy.
3. Name: API Access
4. Assign to: All clients
5. Click Create Policy.

Add a rule to the policy

1. Inside the API Access policy, click Add Rule.
2. Rule Name: Allow API Access
3. Grant type: check Client Credentials.
4. Scopes requested: Any scopes
5. Click Create Rule.

Create a web application

1. Go to Applications > Applications > Create App Integration.
2. Sign-in method: OIDC - OpenID Connect
3. Application type: Web Application
4. App integration name: Kong Gateway
5. Grant types: check Client Credentials.
6. Assignments: Skip group assignment for now
7. Click Save.
8. Copy the Client ID and Client Secret.

Export environment variables

1. Go to Security > API > Authorization Servers.
2. Click the default server.
3. Copy the Issuer URI (for example, https://your-org.okta.com/oauth2/default).

4. Export the following environment variables:

    export DECK_OKTA_ISSUER='https://your-org.okta.com/oauth2/default'
    export DECK_OKTA_CLIENT_ID='your-client-id'
    export DECK_OKTA_CLIENT_SECRET='your-client-secret'
   

   Copied!