HI after Rajini's excellent KIP-85 I am no longer sure KIP-83 needs to exist as is.
Building on top of KIP-85, all it takes to achieve KIP-83 goal is to change the caching of LoginManager on the client side. For example using the new sasl.jaas.config value as the key. This should solve both JIRAs https://issues.apache.org/jira/browse/KAFKA-4180 https://issues.apache.org/jira/browse/KAFKA-3302 Edo -------------------------------------------------- Edoardo Comar IBM MessageHub eco...@uk.ibm.com IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU From: Edoardo Comar/UK/IBM@IBMGB To: dev@kafka.apache.org Date: 28/09/2016 10:55 Subject: Re: [DISCUSS] KIP-83 - Allow multiple SASL PLAIN authenticated Java clients in a single JVM process Thanks Rajini and Harsha I'll update the KIP -------------------------------------------------- Edoardo Comar MQ Cloud Technologies eco...@uk.ibm.com +44 (0)1962 81 5576 IBM UK Ltd, Hursley Park, SO21 2JN IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU From: Rajini Sivaram <rajinisiva...@googlemail.com> To: dev@kafka.apache.org Date: 28/09/2016 10:40 Subject: Re: [DISCUSS] KIP-83 - Allow multiple SASL PLAIN authenticated Java clients in a single JVM process Edo, I was going to write a KIP for this next week :-) I was thinking along the same lines as Harsha, i.e., enable multiple LoginManagers to co-exist in a JVM. The multi-user login module in MessageHub made sense at the time to overcome the limitation in Kafka, without changing Kafka itself. But for the KIP, it would be better to have a solution that supports multiple users for any SASL mechanism. On Wed, Sep 28, 2016 at 5:57 AM, Harsha Chintalapani <ka...@harsha.io> wrote: > Edorado, > Thanks for the KIP. As pointed out in the JIRA can you make > sure this is not just a specific change for SASL plain but make changes in > general to LoginManager such that its not a singleton. > > Thanks, > Harsha > > On Tue, Sep 27, 2016 at 10:15 AM Edoardo Comar <eco...@uk.ibm.com> wrote: > > > Hi, > > I had a go at a KIP that addresses this JIRA > > https://issues.apache.org/jira/browse/KAFKA-4180 > > "Shared authentification with multiple actives Kafka producers/consumers" > > > > which is a limitation of the current Java client that we (IBM MessageHub) > > get asked quite often lately. > > > > We will have a go at a PR soon, just as a proof of concept, but as it > > introduces new public interfaces it needs a KIP. > > > > I'll welcome your input. > > > > Edo > > -------------------------------------------------- > > Edoardo Comar > > MQ Cloud Technologies > > eco...@uk.ibm.com > > +44 (0)1962 81 5576 > > IBM UK Ltd, Hursley Park, SO21 2JN > > > > IBM United Kingdom Limited Registered in England and Wales with number > > 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. > PO6 > > 3AU > > Unless stated otherwise above: > > IBM United Kingdom Limited - Registered in England and Wales with number > > 741598. > > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 > 3AU > > > -- Regards, Rajini Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU