You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2016/06/23 06:33:16 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=15345885#comment-15345885 ] 

Enrico Olivelli commented on BOOKKEEPER-391:
--------------------------------------------

maybe we can add a generic support for SASL and then add support for GSSAPI, which requires some more coding

> 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: Rakesh R
>
> 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)