Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Tue, 13 Jan 2015 23:56:35 +0000 (UTC)
From: "Mike Drob (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12714568.1400178712000.76407.1421193395017@Atlassian.JIRA>
In-Reply-To: <JIRA.12714568.1400178712000@Atlassian.JIRA>
References: <JIRA.12714568.1400178712000@Atlassian.JIRA>
 <JIRA.12714568.1400178712438@arcas>
Subject: [jira] [Commented] (ACCUMULO-2815) Kerberos authentication for
 clients
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276222#comment-14276222 ] 

Mike Drob commented on ACCUMULO-2815:
-------------------------------------

What do the headings mean?

> Kerberos authentication for clients
> -----------------------------------
>
>                 Key: ACCUMULO-2815
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2815
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> We have server authentication via Kerberos, but we don't have a way for clients to connect to Accumulo using Kerberos.
> HBase context: http://hbase.apache.org/book/security.html#d248e5472
> We'll have to look into how Authorizations and Permissions are assigned to these users and make sure the ZK-backed security mechanisms can still support this. It would be nice to not have to make a completely separate auth/permission mechanism when kerberos is being used.
> As far as configuration, I imagine this would be a great fit for the often-proposed client-side configuration idea.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)