zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Han (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3558) Support authentication enforcement
Date Thu, 26 Sep 2019 04:00:13 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938245#comment-16938245

Michael Han commented on ZOOKEEPER-3558:

FYI ZOOKEEPER-1634 introduced an option that user can choose to enforce authentication such
as unauthenticated clients will not be able to connect to ZooKeeper, which solves problem

> Support authentication enforcement
> ----------------------------------
>                 Key: ZOOKEEPER-3558
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3558
>             Project: ZooKeeper
>          Issue Type: New Feature
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>             Fix For: 3.5.7
>         Attachments: ZOOKEEPER-3558-01.patch
> Provide authentication enforcement in ZooKeeper that is backward compatible and can work
for any authentication scheme, can work even with custom authentication schemes.
> *Problems:*
> 1. Currently server is starting with default authentication providers(DigestAuthenticationProvider,
IPAuthenticationProvider). These default authentication providers are not really secure.
> 2. ZooKeeper server is not checking whether authentication is done or not before performing
any user operation.
> *Solutions:*
> 1. We should not start any authentication provider by default. But this would be backward
incompatible change. So we can provide configuration whether to start default authentication
provides are not.
> By default we can start these authentication providers.
> 2. Before any user operation server should check whether authentication happened or not.
At least client must be authenticated with one authentication scheme.

This message was sent by Atlassian Jira

View raw message