-
Currently, components authenticate each other based on SASL PLAIN. However, under the hood, the server components forward the credentials provided by the client to Hono Auth in order to retrieve a JWT…
-
### I don't see any examples for kafka producer/consumer with OAUTHBEARER, Azure AD and Kafka OIDC.
The default OAuth Authentication via [SASL/OAUTHBEARER for Kafka](https://cwiki.apache.org/conflu…
-
**Describe the bug**
When a consumer's connection outlives its SASL authentication (in this case an OAuth token), then consumer will fail to fetch new records because the broker no longer accepts any…
-
When using IBM EventStreams/Kafka the authentication mechanism is via username/password using the `PLAIN` SASL Mechanism. This can be partially seen in [`microprofile-config.properties`](https://gith…
-
# Description
Currently, client credentials that we issue to users through https://gcn.nasa.gov/quickstart are good for exactly one group/scope. The reason is that we are transforming the scope cla…
-
Description
===========
Admin client cannot connect to the bootstrap servers when using `SASL_SSL` with `OAUTHBEARER`.
I'm trying to connect to AWS MSK cluster bootstrap servers. Admin client can c…
-
Hi, currently I'm seeing that we only support the basic auth for `SchemaRegistry`, with username/password. I wonder if there is another way to get Oauth bear token like kafkajs has for broker authenti…
-
cfk operator version: 2.50
OpenShift version: 4.9
I was trying to create a connect cluster in OpenShift that needs to connect to an on-prem Kafka Brokers. My CRD instance definition is as follows,…
-
Hello,
I'm trying to connect to my Kafka Broker using SASL. I'm using the docker version 0.20.0. I can successfully connect to the broker when running
`kafka-topics --bootstrap-server broker:90…
-
Hi all,
I configured my company email account with OAUTHBEARER and can read all emails.
However, I cannot reply to the email with "Oauth token is too big:250" message.
Based on this https://unix…
Ruach updated
2 months ago