Confluent Consume Policy

Premium Partner

Confluent Schema Registry with OAuth2

Use the Confluent Schema Registry for message deserialization and secure it with OAuth 2.0 token authentication.

Prerequisites

  • A Kafka cluster in Confluent Cloud.

  • A Kafka topic in the cluster.

  • An API key and secret for the cluster.

  • A Schema Registry.

  • An identity provider that supports the OAuth 2.0 client credentials grant, such as Keycloak or Okta.

Environment variables

  • BOOTSTRAP_SERVER_HOST: The bootstrap server host.

  • API_KEY: The API key to use for authentication.

  • API_SECRET: The API secret to use for authentication.

  • KAFKA_TOPIC: The name of the Kafka topic to consume from.

  • REGISTRY_URL: The URL of your Confluent Schema Registry instance. For example, http://schema-registry:8081.

  • CLIENT_ID: The client ID that the policy uses when it calls authenticated endpoints of the identity provider.

  • CLIENT_SECRET: The client secret from the identity provider.

Set up the policy

Attach the policy

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!