GitHub user haoch opened a pull request:

    https://github.com/apache/incubator-eagle/pull/256

    EAGLE-360 Kafka Java Producer with kerberos

    https://issues.apache.org/jira/browse/EAGLE-360
    
    `log4j.properties`
    ~~~
    log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL
    log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Conf=/etc/krb5.conf
    
log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthLoginConfig=/etc/kafka/kafka_jaas.conf
    log4j.appender.KAFKA_HDFS_AUDIT.SecurityAuthUseSubjectCredsOnly=false
    log4j.appender.KAFKA_HDFS_AUDIT.SecurityKrb5Debug=true
    
    `kafka_jaas.conf`
    ~~~
    KafkaClient {
        com.sun.security.auth.module.Krb5LoginModule required
        doNotPrompt=true
        useTicketCache=true
        principal="[email protected]"
        useKeyTab=true
        serviceName="kafka"
        keyTab="/etc/security/keytabs/ctadmin.keytab"
        client=true;
    }
    ~~~

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/haoch/incubator-eagle EAGLE-360

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-eagle/pull/256.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #256
    
----
commit 6b4671f1981d38733ac77dcf1988b27bb50f58ee
Author: Hao Chen <[email protected]>
Date:   2016-07-10T02:56:53Z

    EAGLE-360 Support 
log4j.appender.KAFKA_HDFS_AUDIT.SecurityProtocol=PLAINTEXTSASL

commit c78a335e5000242830c929b6c56a00b9e5dcba0e
Author: Hao Chen <[email protected]>
Date:   2016-07-10T03:15:45Z

    EAGLE-360 Support 
SecurityKrb5Conf/SecurityAuthLoginConfig/SecurityAuthUseSubjectCredsOnly/SecurityKrb5Debug
 in log4j.properties configuration as an alternative solution then passing 
through system properties with -D

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to