You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Jonathan Maron (JIRA)" <ji...@apache.org> on 2015/06/24 21:29:04 UTC

[jira] [Resolved] (ATLAS-32) Atlas hook fails to fire in certain secure deployments

     [ https://issues.apache.org/jira/browse/ATLAS-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Maron resolved ATLAS-32.
---------------------------------
    Resolution: Fixed

Commit: 15639ee996f6a6b09f3d328b8a1a876385c6f373 [15639ee]
Parents: d6f5d9da69
Author: Jon Maron <jm...@hortonworks.com>
Date: June 24, 2015 at 3:24:52 PM EDT
Labels: origin/master origin/HEAD master

ATLAS-32 create HTTP connection in context of invoking user in secure cluster

> Atlas hook fails to fire in certain secure deployments
> ------------------------------------------------------
>
>                 Key: ATLAS-32
>                 URL: https://issues.apache.org/jira/browse/ATLAS-32
>             Project: Atlas
>          Issue Type: Bug
>    Affects Versions: 0.5-incubating
>            Reporter: Jonathan Maron
>            Assignee: Jonathan Maron
>            Priority: Critical
>             Fix For: 0.5.1-incubating
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> In certain secure deployments, the interactions from hive to atlas trigger security exceptions like the following:
> 2015-06-20 07:29:00,506 INFO  [Atlas Logger 0]: hook.HiveHook (HiveHook.java:run(154)) - Atlas hook failed
> com.sun.jersey.api.client.ClientHandlerException: java.io.IOException: org.apache.hadoop.security.authentication.client.AuthenticationException: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)
> this is more than likely due the need to perform the interactions as an identity that has an associated kerberos ticket.



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