Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 21 Apr 2014 18:42:14 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12709598.1398105463485.149280.1398105734744@arcas>
In-Reply-To: <JIRA.12709598.1398105463485@arcas>
References: <JIRA.12709598.1398105463485@arcas>
Subject: [jira] [Commented] (ACCUMULO-2705) Figure out internal
 authentication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser commented on ACCUMULO-2705:
--------------------------------------

Relevant issue if I try to use !SYSTEM:

{noformat}
org.apache.accumulo.core.client.AccumuloSecurityException: Error USER_DOESNT_EXIST for user !SYSTEM on table replication(?) - The user does not exist
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:327)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doFateOperation(TableOperationsImpl.java:302)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.doTableFateOperation(TableOperationsImpl.java:1591)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.create(TableOperationsImpl.java:229)
	at org.apache.accumulo.core.client.admin.TableOperationsImpl.create(TableOperationsImpl.java:193)
{noformat}

> Figure out internal authentication
> ----------------------------------
>
>                 Key: ACCUMULO-2705
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2705
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> When creating a table to use for storing replication "bookkeeping", I found that the internal !SYSTEM user doesn't have the ability to create a table. Should it?
> Without this, the user would have to create/configure a custom local user account with proper credentials to read/write the replication table as well as persist this in accumulo-site.xml. My first impression is that this is excessive waste because the usage is purely within the tablet server already -- need to try to figure out if there's a reason that !SYSTEM shouldn't be allowed to create tables.


--
This message was sent by Atlassian JIRA
(v6.2#6252)