You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2016/10/06 14:21:20 UTC

[jira] [Created] (ACCUMULO-4489) Monitor login for trace viewing should fall back to GENERAL_KERBEROS_KEYTAB to match behavior of trace server

Sean Busbey created ACCUMULO-4489:
-------------------------------------

             Summary: Monitor login for trace viewing should fall back to GENERAL_KERBEROS_KEYTAB to match behavior of trace server
                 Key: ACCUMULO-4489
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4489
             Project: Accumulo
          Issue Type: Bug
          Components: monitor, trace
    Affects Versions: 1.7.2, 1.7.1
            Reporter: Sean Busbey
            Assignee: Sean Busbey
            Priority: Critical
             Fix For: 1.7.3, 1.8.1, 2.0.0


The current kerberos instructions rely on the trace user falling back to the GENERAL_KERBEROS_KEYTAB when kerberos for client access is enabled. This works as expected on the TraceServer, but the Monitor's servlet for viewing traces only uses the trace keytab.

workaround is to use the undocumented {{trace.token.property.keytab}} property to specify the appropriate keytab.

Even once the trace user keytab property is documented in ACCUMULO-4488, we should make the behavior match that in the TraceServer.



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