accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3454) ZooZap should use server login, not client options
Date Wed, 31 Dec 2014 00:39:14 GMT

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

Christopher Tubbs commented on ACCUMULO-3454:
---------------------------------------------

I think there's a lot of server utils that do this. I noticed that with the ClientContext
changes. Could just look for and review all the uses of JCommander client opts in the server
jars.

> ZooZap should use server login, not client options
> --------------------------------------------------
>
>                 Key: ACCUMULO-3454
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3454
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> I noticed an oddity working on Kerberos where I could start Accumulo as myself (which
is expected since we have keytabs for the servers to login), but shutting down Accumulo would
fail because I didn't have credentials.
> Looking into this, one thing we need is for ZooZap to login as the server user, not as
a client. The program needs access to accumulo-site.xml to operate, so it's expected that
this lives in "server land" and is not a client application.



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

Mime
View raw message