[
https://issues.apache.org/jira/browse/BOOKKEEPER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024722#comment-16024722
]
Hudson commented on BOOKKEEPER-391:
-----------------------------------
FAILURE: Integrated in Jenkins build bookkeeper-master #1760 (See
[https://builds.apache.org/job/bookkeeper-master/1760/])
BOOKKEEPER-391: Support Kerberos authentication of bookkeeper (eolivelli: rev
667390d1a6305c31608130929ba0d68a0b5a4763)
* (add)
bookkeeper-server/src/test/java/org/apache/bookkeeper/sasl/MD5DigestBookKeeperTest.java
* (edit) bookkeeper-server/pom.xml
* (add)
bookkeeper-server/src/test/java/org/apache/bookkeeper/sasl/GSSAPIBookKeeperTest.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SaslServerState.java
* (add) bookkeeper-server/src/test/resources/jaas_md5.conf
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/JAASCredentialsContainer.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SASLBookieAuthProviderFactory.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SaslClientState.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SASLClientAuthProvider.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SaslConstants.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SASLBookieAuthProvider.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/SASLClientProviderFactory.java
* (add)
bookkeeper-server/src/main/java/org/apache/bookkeeper/sasl/TGTRefreshThread.java
> 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)
