[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh R updated BOOKKEEPER-391:
--------------------------------

    Description: 
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. 

  was:
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. The BK also could manage and renew 
users authenticated to BK via Kerberos. There is currently no configuration or 
hooks for the Bookie process to obtain Kerberos credentials.

Also today an unauthenticated bookie client can easily establish connection 
with the bookkeeper server. 


    
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to