ASF GitHub Bot commented on KAFKA-4301:

GitHub user rajinisivaram opened a pull request:


    KAFKA-4301: Add more trace for SSL handshake


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

    $ git pull https://github.com/rajinisivaram/kafka KAFKA-4301

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


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

    This closes #2027
commit 8ef6ad6d7f465224be73166077f5a9394fff48c1
Author: Rajini Sivaram <rajinisiva...@googlemail.com>
Date:   2016-10-14T09:03:05Z

    KAFKA-4301: Add more trace for SSL handshake


> Include some SSL/TLS logging to avoid need need for javax debug util every 
> time an issue arises 
> ------------------------------------------------------------------------------------------------
>                 Key: KAFKA-4301
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4301
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Ryan P
>            Assignee: Rajini Sivaram
> It would be handy to include certain transport layer session attributes in at 
> least the debug level logging within Kafka. Specifically with regard to 
> TLS/SSL communications. 
> Some of the things it would be helpful to see without having to enable the 
> javax network debug utility include: 
> 1. Negotiated cipher suite 
> 2. Authenticated client principal 
> Technically item2 is covered with the authorizer logging but it would be nice 
> to have this information available even in the absence of an authorizer 
> implementation. 

This message was sent by Atlassian JIRA

Reply via email to