Support for SSL for the connection to Schema Registry is needed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from confluentinc/libserdes
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
confluentinc/libserdes#68 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
confluentinc/libserdes#66 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
confluentinc/libserdes#64 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
confluentinc/libserdes#63 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
confluentinc/libserdes#59 · 2 comments ·
All issues in confluentinc/libserdes
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
arduino/ArduinoCore-mbed#1126 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
security
Difficulty 1/5 Under an hour Newbie friendliness 93/100
btclib-org/btclib-secp256k1#1427 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
esmuellert/codediff.nvim#594 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 67/100