Issue with POST Request to Schema Registry for Caching Schema (403 Forbidden Error)

[github-Gaurav]

We are encountering an issue when attempting to deserialize Avro messages using the Confluent Avro Converter. Our use case involves accessing an Avro schema registry via a GET request only. As a result, we only have GET access to the schema registry to download schemas for deserialization.

However, when attempting to deserialize Avro messages, the converter makes a POST request to the schema registry. This request is used for verifying the schema's authenticity and caching it for future use. Unfortunately, since our access to the schema registry is limited to GET requests, we are receiving a 403 Forbidden error when the POST request is made, causing the deserialization to fail.

Problem Details:

• The Avro Converter is making a POST request to the schema registry to check the authenticity of the schema and cache it.
• We only have GET access to the schema registry and do not have permission to make POST requests.
• This results in a 403 Forbidden error, which prevents the Avro messages from being deserialized correctly.

Expected Behavior:

We expect that the Avro Converter would only use GET requests to retrieve the schema from the schema registry for deserialization purposes, especially when schema verification and caching are unnecessary or can be performed in an alternative way.

Possible Workaround:

As a potential workaround, it would be helpful if the converter could:

1. Skip the POST request for schema verification and caching if it is not required for deserialization.
2. Provide an option to disable this behavior, allowing us to continue using GET requests only to access the schema.

Alternatively, it would be great if the converter could be modified to allow users to specify whether caching or schema verification via POST is required and provide a configuration option to disable it.

Questions:

1. Is there any configuration or workaround to prevent the Avro Converter from making POST requests to the schema registry while still deserializing Avro messages?
2. Can the converter's behavior be modified to allow for schema deserialization using only GET requests, without requiring POST access to the schema registry?

We would appreciate any insights or guidance on resolving this issue, or if this is something that could potentially be addressed in future updates to the converter.

Thanks