[
https://issues.apache.org/jira/browse/BOOKKEEPER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870136#comment-15870136
]
ASF GitHub Bot commented on BOOKKEEPER-391:
-------------------------------------------
GitHub user eolivelli opened a pull request:
https://github.com/apache/bookkeeper/pull/110
BOOKKEEPER-391 Support Kerberos authentication of bookkeeper
This patch contains a very basic AuthProvider which uses JAAS and so
enables the usage or GSSAPI/Kerberos for BookKeeper authentication
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/eolivelli/bookkeeper BOOKKEEPER-391-kerberos
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bookkeeper/pull/110.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 #110
----
commit d4a26c8dbde264a95dfb055c6775b07915ee757c
Author: eolivelli <[email protected]>
Date: 2016-10-21T15:14:31Z
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
> 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)
