[BOOKKEEPER-391] Support Kerberos authentication of bookkeeper

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.5.0
• Component/s: bookkeeper-client, bookkeeper-server
• Assignee: Enrico Olivelli
• Reporter: Rakesh Radhakrishnan
• Created: 04/Sep/12 17:11
• Updated: 25/May/17 13:23
• Resolved: 25/May/17 11:32

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.

Issue Links

• is related to: BOOKKEEPER-959 ClientAuthProvider and BookieAuthProvider Public API used Protobuf Shaded classes
• is related to: BOOKKEEPER-969 Security Support
• relates to: BOOKKEEPER-901 Add an authentication framework
• links to: GitHub Pull Request #85
• links to: GitHub Pull Request #110
• mentioned in: Page Loading...

Sub-Tasks

• Create documentation for JAAS and Kerberos configuration: Resolved