Support full OAUTHBEARER properties

[carlosfwrk]

Users

• Development manager tasked with ensuring a team is successful in using streaming data
• Developer on a team tasked with building new features using streaming data
• Developer at an org who manages a streaming platform while building new features that use streaming data
• Developer tasked with building pipelines for use in business analytics
• Other: [User type] tasked with [primary goal in the realm of streaming data]

Problems

The plugin only allows a limited set of OAUTHBEARER properties, preventing connections to clusters with custom configurations.

Solutions

Enable users to provide any Kafka connection property, either via the UI form or by importing a JSON/properties file.

Goals

Allow full flexibility for cluster connections, not just the predefined fields (bootstrap.servers, security.protocol, sasl.mechanism, token.endpoint.url, clientId, clientSecret)

Non-Goals

No response

Background

Many OAUTHBEARER clusters require additional properties. Without full property support, the plugin cannot connect unless defaults are already configured.

Proposal

Consider supporting a Kafka properties file similar to kafka-avro-console-producer for advanced configurations.

[carlosfwrk]

For example, I need to set custom OAUTHBEARER properties to connect to my Kafka clusters:
sasl.oauthbearer.sub.claim.name=scp
Without the ability to specify this, the plugin cannot connect to these clusters.