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/08/24 14:22:20 UTC
[jira] [Updated] (ACCUMULO-4421) TraceServer should fall back to
GENERIC_KERBEROS_PRINCIPAL when trace specific kerberos settings are not
present
[ https://issues.apache.org/jira/browse/ACCUMULO-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey updated ACCUMULO-4421:
----------------------------------
Status: Patch Available (was: In Progress)
> TraceServer should fall back to GENERIC_KERBEROS_PRINCIPAL when trace specific kerberos settings are not present
> ----------------------------------------------------------------------------------------------------------------
>
> Key: ACCUMULO-4421
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4421
> Project: Accumulo
> Issue Type: Bug
> Components: trace
> Affects Versions: 1.7.2, 1.7.1
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 1.8.0
>
> Attachments: ACCUMULO-4421.1.patch
>
>
> Prior to 1.7, the TraceServer always started using the same server utils as the other daemons. Since a trace server has to talk to Accumulo and that might involve needing a Kerberos Identity in 1.7+, it was switched to its own setup.
> Currently that setup will default back to GENERIC_KERBEROS_KEYTAB if a keytab isn't specified for the trace user, but it will simply exit early if there isn't a principal defined for hte trace user. It should instead default to the GENERIC_KERBEROS_PRINCIPAL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)