accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4488) fix gaps in user manual section on Kerberos for clients
Date Thu, 06 Oct 2016 19:39:20 GMT

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

Mike Drob commented on ACCUMULO-4488:
-------------------------------------

bq. +Note that on an existing cluster the server side changes will a full cluster shutdown
and restart. You should
Missing a word.

bq. +- version: 1.7.2
I was going to ask if this should be 1.8.0, but spot checking our docs we are not consistent
on this at all.

bq. +*A*: This indicates that the Monitor has not been able to successfully log in a client-side
user to read from the +trace+ table. Accumulo allows the TraceServer to rely on the property
+general.kerberos.keytab+ as a fallback when logging in the trace user if the +trace.token.property.keytab+
property isn't defined. Some earlier versions of Accumulo did not do this same fallback for
the Monitor's use of the trace user. The end result is that if you just configure +general.kerberos.keytab+
you will end up with a system that properly logs trace information but can't view it.
nit: remove "just"

> fix gaps in user manual section on Kerberos for clients 
> --------------------------------------------------------
>
>                 Key: ACCUMULO-4488
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4488
>             Project: Accumulo
>          Issue Type: Bug
>          Components: docs
>    Affects Versions: 1.7.1, 1.7.2
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>         Attachments: ACCUMULO-4488.1.patch
>
>
> clean up several gaps in the docs that I stumbled on while setting up a cluster with
kerberos for clients:
> * document setting up a superuser on an existing system that's enabling kerberos
> * include example of verifying access for the superuser
> * per-user client configuration gives wrong filename
> * per-user client configuration required additions for kerberos missing {{rpc.sasl.qop}}
> * document {{trace.token.property.keytab}}
> * note required permissions for trace user (Table.READ, Table.WRITE, Table.ALTER_TABLE)



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

Mime
View raw message