Hi Ron, Now that login callback handlers are configurable, is this KIP still a pre-req for OAuth? I was wondering whether we still need the ability to add new substitutable types or whether it would be sufficient to add the built-in ones to read from file etc.
On Thu, Mar 29, 2018 at 6:48 AM, Ron Dagostino <rndg...@gmail.com> wrote: > Hi everyone. There have been no comments on this KIP, so I intend to put > it to a vote next week if there are no comments that might entail changes > between now and then. Please take a look in the meantime if you wish. > > Ron > > On Thu, Mar 15, 2018 at 2:36 PM, Ron Dagostino <rndg...@gmail.com> wrote: > > > Hi everyone. > > > > I created KIP-269: Substitution Within Configuration Values > > <https://cwiki.apache.org/confluence/display/KAFKA/KIP+ > 269+Substitution+Within+Configuration+Values> > > (https://cwiki.apache.org/confluence/display/KAFKA/KIP+269+ > > Substitution+Within+Configuration+Values > > <https://cwiki.apache.org/confluence/pages/viewpage. > action?pageId=75968876> > > ). > > > > This KIP proposes adding support for substitution within client JAAS > > configuration values for PLAIN and SCRAM-related SASL mechanisms in a > > backwards-compatible manner and making the functionality available to > other > > existing (or future) configuration contexts where it is deemed > appropriate. > > > > This KIP was extracted from (and is now a prerequisite for) KIP-255: > > OAuth Authentication via SASL/OAUTHBEARER > > <https://cwiki.apache.org/confluence/pages/viewpage. > action?pageId=75968876> > > based on discussion of that KIP. > > > > Ron > > >
