Ah, I figured out the issue. It was user error. I needed to add that config to my connectors ConfigDef, and after that everything was working just fine.
On Fri, Feb 24, 2017 at 1:41 PM, Ismael Juma <isma...@gmail.com> wrote: > I suggest filing a JIRA with the details to reproduce and the stacktrace. > The way it works for the consumer/producer is that the string config gets > converted into a Password instance during the parsing stage. Seems like > this is not happening in the connect case for some reason. > > Ismael > > On 24 Feb 2017 5:56 pm, "Stephen Durfey" <sjdur...@gmail.com> wrote: > > > Yes, if I set jaas.sasl.config in my connector config it results in a > > ClassCastException thrown by JaasUtils when it retrieves that key from > the > > config map. It's doing an explicit cast to Password, but I he value type > is > > String at that point. > > > > > > > > > > > > > > On Fri, Feb 24, 2017 at 11:30 AM -0600, "Ismael Juma" <ism...@juma.me.uk > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > Hi Stephen, > > > > Did you get an error when you set this as a String? It should work fine. > > > > Ismael > > > > On Thu, Feb 23, 2017 at 8:09 PM, Stephen Durfey wrote: > > > > > Now that 0.10.2.0 is out, I was looking forward to checking out the > > > inclusion of KIP-85 > > > configuration+for+Kafka+clients>. > > > I have a potential need for multi-tenancy in a single kafka connect > > > instance, and wanted to be able to authenticate each connector via > > > kerberos, and setting up ACLs for the principal to control read/write > > > access. I'm not seeing a way to specify the config key > 'sasl.jaas.config' > > > on the connector config, as it is read in as a string, but JaasUtils > (and > > > looks like now LoginManager in trunk) expects the type to already be > > > PASSWORD. > > > > > > Is there a way in connect to make this work now, or should I log a > > JIRA/KIP > > > for this enhancement? > > > > > > Thanks, > > > Stephen > > > > > > > > > > > > > > > >
