This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • KIP-425: Add some Log4J Kafka Appender Properties for Producing to Secured Brokers
Skip to end of metadata
Go to start of metadata

Status

Current stateAccepted

Discussion thread: here

JIRAKAFKA-7896

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

The existing Log4J Kafka appender supports producing to brokers that use the GSSAPI (kerberos) sasl mechanism, and only supports configuring jaas via setting the jaas config file as a jvm property. This KIP covers extending this to include the PLAIN mechanism and to support configuring jaas via a property passed to the producer.

Public Interfaces

We propose adding two new config properties to the log4j appender:

  • SaslMechanism: The value for this config will be put into the "sasl.mechanism" property passed to the producer created by KafkaLog4jAppender. If no value is provided for this property, then no value will be set for "sasl.mechanism" (which is the current behavior).
  • ClientJaasConf: The value for this config will be put into the "saasl.jaas.config" property passed to the producer created by KafkaLog4jAppender. If no value is provided for this property, then no value will be set for "sasl.jaas.config" (which is the current behavior).

Proposed Changes

The Public Interfaces section covers the proposed changes.

Compatibility, Deprecation, and Migration Plan

The proposal only changes behavior if the new configs are specified, so there are no compatibility concerns.

Rejected Alternatives

N/A

  • No labels