[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696219#comment-15696219
 ] 

ASF GitHub Bot commented on BOOKKEEPER-391:
-------------------------------------------

GitHub user eolivelli opened a pull request:

    https://github.com/apache/bookkeeper/pull/85

    BOOKKEEPER-391 Support Kerberos authentication of bookkeeper

    This patch is based on work for BOOKKEEPER-959. Please consider only the 
second commit

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

    $ git pull https://github.com/eolivelli/bookkeeper BOOKKEEPER-391-sasl

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

    https://github.com/apache/bookkeeper/pull/85.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 #85
    
----
commit e851e10c8cb259bc84a5d6b4290eec6dd2c1318e
Author: eolivelli <eolive...@gmail.com>
Date:   2016-10-20T14:18:34Z

    BOOKKEEPER-959 ClientAuthProvider and BookieAuthProvider Public API used 
Protobuf Shaded classes

commit 8d2d560ab2cafcef050852ce8ae6e2b8786fde85
Author: eolivelli <eolive...@gmail.com>
Date:   2016-11-25T15:23:37Z

    BOOKKEEPER-391 Support Kerberos authentication of bookkeeper

----


> Support Kerberos authentication of bookkeeper
> ---------------------------------------------
>
>                 Key: BOOKKEEPER-391
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-391
>             Project: Bookkeeper
>          Issue Type: New Feature
>          Components: bookkeeper-client, bookkeeper-server
>            Reporter: Rakesh R
>            Assignee: Enrico Olivelli
>
> This JIRA to discuss authentication mechanism of bookie clients and server. 
> Assume ZK provides fully secured communication channel using Kerberos based 
> authentication and authorization model. We could also manage and renew users 
> authenticated to BK via Kerberos. There is currently no configuration or 
> hooks for the Bookie process to obtain Kerberos credentials.
> Today an unauthenticated bookie client can easily establish connection with 
> the bookkeeper server. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to