accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2705) Figure out internal authentication
Date Mon, 21 Apr 2014 19:28:15 GMT

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

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

bq. Actually, this may be as simple as changing the CreateTable FATE op to not try to grant
permissions on the table being created when the user who initiated the creation is !SYSTEM

Turns out it was. I don't see any issues with that approach either, so this is the best of
both worlds IMO.

> 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)

Mime
View raw message