Re: [VOTE] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

; +1 (non-binding) > > > > Apologies. I thought I’d already voted :( > > > > > On Apr 7, 2024, at 10:48 AM, Nelson B. > wrote: > > > > > > Hi all, > > > > > > Just wanted to bump up this thread for visibility. > > > >

Re: KIP-919: Allow AdminClient to Talk Directly with the KRaft Controller Quorum

Hi Colin, Thanks for the KIP! I'm sorry for reopening this old discussion thread but I don't know where else I can ask my question. I wanted to use the newly updated kafka-configs.sh tool to dynamically update the ssl keystore in the controller node, but I still couldn't figure it out. Is it

Re: [VOTE] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

Hi all, Just wanted to bump up this thread for visibility. Thanks! On Thu, Mar 28, 2024 at 3:40 AM Doğuşcan Namal wrote: > Thanks for checking it out Nelson. Yeah I think it makes sense to leave it > for the users who want to use it for testing. > > On Mon, 25 Mar 2024 at 20:

Re: [VOTE] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

t would be good to double check. Sending secrets over > plaintext is a security bad practice :) > > +1 (non-binding) from me. > > On Tue, 19 Mar 2024 at 16:00, Nelson B. wrote: > > > Hi all, > > > > I would like to start a vote on KIP-1025 > > < > > >

[VOTE] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

Hi all, I would like to start a vote on KIP-1025 , which would optionally URL-encode clientID and clientSecret in the authorization header. I feel like all

Re: [DISCUSS] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

if everyone else is cool with > it :) > > Thanks, > Kirk > > > On Mar 13, 2024, at 5:31 AM, Nelson B. wrote: > > > > Hi all, > > > > I just wanted to bump up this thread. > > > > The KIP introduces a really small change and PR is already read

Re: [DISCUSS] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

Hi all, I just wanted to bump up this thread. The KIP introduces a really small change and PR is already ready and only waiting for this KIP to get approved to be merged. Thanks, On Wed, Mar 6, 2024 at 12:26 PM Nelson B. wrote: > Hi all, > > I would like to start a discussion on

[DISCUSS] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

Hi all, I would like to start a discussion on KIP-1025, which would optionally URL-encode clientID and clientSecret in the authorization header https://cwiki.apache.org/confluence/display/KAFKA/KIP-1025%3A+Optionally+URL-encode+clientID+and+clientSecret+in+authorization+header Best, Nelson B.

[jira] [Created] (KAFKA-16345) Optionally allow urlencoding clientId and clientSecret in authorization header

Nelson B. created KAFKA-16345: - Summary: Optionally allow urlencoding clientId and clientSecret in authorization header Key: KAFKA-16345 URL: https://issues.apache.org/jira/browse/KAFKA-16345 Project

Dynamically update controller configuration

Hello everyone, I want to ask how or if is it possible to dynamically update controller( process.roles=controller) configurations in KRaft mode. We are using short-lived certificates for server authentication so we want to be able to dynamically update keystore and truststore. "kafka-configs"

Re: EmbeddedKafkaCluster not working with SASL

create a ticket and work on this. Also, I'm still not able to resolve the issue with SASL in EmbeddedKafkaCluster. Thanks, On Thu, Nov 9, 2023 at 6:05 PM Nelson B. wrote: > Hello, > > I am utilizing > "org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster" to wri

EmbeddedKafkaCluster not working with SASL

Hello, I am utilizing "org.apache.kafka.streams.integration.utils.EmbeddedKafkaCluster" to write integration tests for my application. In general, things are functioning properly. However, when I modify the default server configurations to use a SASL_PLAINTEXT listener with the PLAIN mechanism,

Re: [DISCUSS] KIP-973 Expose per topic replication rate metrics

Hi all, I just wanted to bump up this discussion thread. Can you please share your opinion? Thanks On Fri, Sep 8, 2023 at 5:10 PM Nelson B. wrote: > Hi all, > > I just wanted to bump up this discussion thread. > > Thanks > > On Thu, Aug 31, 2023 at 2:05 AM Nel

Re: [DISCUSS] KIP-973 Expose per topic replication rate metrics

Hi all, I just wanted to bump up this discussion thread. Thanks On Thu, Aug 31, 2023 at 2:05 AM Nelson Bighetti wrote: > Relatively minor change that fixes a mismatch between documentation and > implementation. > >