[
https://issues.apache.org/jira/browse/KAFKA-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491532#comment-15491532
]
Ewen Cheslack-Postava commented on KAFKA-4171:
----------------------------------------------
Yeah, that's almost definitely what's happening [~criccomini]. I'm not sure
that actually stripping them out will solve this problem though because the
consumer.* prefixed version will probably also be printed by the worker config.
We can try to remove the settings in each case, although this is also just a
more general problem with the way Kafka handles configs (e.g. a sensitive
serializer setting, e.g. something like SSL settings for a schema registry,
can't possibly be known by the framework and so would always be logged). So I
think we can fix this immediate issue, but the way configs are logged might
still be an issue.
> Kafka-connect prints outs keystone and truststore password in log2
> ------------------------------------------------------------------
>
> Key: KAFKA-4171
> URL: https://issues.apache.org/jira/browse/KAFKA-4171
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.10.0.0
> Reporter: Akshath Patkar
> Assignee: Ewen Cheslack-Postava
>
> Kafka-connect prints outs keystone and truststore password in log
> [2016-09-14 16:30:33,971] WARN The configuration
> consumer.ssl.truststore.password = XXXXX was supplied but isn't a known
> config. (org.apache.kafka.clients.consumer.ConsumerConfig:186)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
