Support for SSL for the connection to Schema Registry is needed

Open
#40 0 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
api, security

Research direction

Start by locating the libserdes Schema Registry REST connection code and its existing configuration options. Use the kafkacat command and SSL keystore settings in the report as the reproduction case; done means a client certificate and keystore can be configured for a successful Schema Registry connection.

Written by the indexing model from the issue text.

Description

Support for SSL certificates and keystores configuration options for the connection to Schema Registry is needed.

Currently, this is not possible to connect to Schema Registry, requiring client SSL certificate, with libserdes:

$ ./kafkacat -b $KAFKA_BROKER_HOST:$KAFKA_BROKER_PORT \
> -t my-topic \
> -s value=avro \
> -r https://$KAFKA_API_KEY:$KAFKA_API_SECRET@$KAFKA_SCHEMA_REGISTRY_HOST:$KAFKA_SCHEMA_REGISTRY_PORT \
> -X security.protocol=SASL_SSL \
> -X sasl.mechanisms=PLAIN \
> -X sasl.username="$KAFKA_API_KEY" -X sasl.password="$KAFKA_API_SECRET" \
> -X ssl.keystore.location=$KAFKA_KEYSTORE_P12_LOCATION \
> -X ssl.keystore.password=$KAFKA_KEYSTORE_PASSPHRASE \
> -X ssl.key.password=$KAFKA_KEY_PASSPHRASE \
> -X enable.ssl.certificate.verification=false \
> -o beginning -C
% ERROR: Failed to format message in my-topic [0] at offset 2: Avro/Schema-registry message deserialization: REST request failed (code -1): HTTP request failed: SSL connect error : terminating
Dominant language
C
Stars
12
Forks
62
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from confluentinc/libserdes

All issues in confluentinc/libserdes

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.