You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/16 14:25:41 UTC

[jira] [Commented] (BOOKKEEPER-391) Support Kerberos authentication of bookkeeper

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

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

Github user eolivelli closed the pull request at:

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


> 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
>             Fix For: 4.5.0
>
>
> 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.15#6346)