[jira] [Commented] (SENTRY-1052) Sentry shell should use kerberos requestor and give better error messages for kerberos failures

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on SENTRY-1052:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12786442/SENTRY-1052.patch against master.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/1162/console

This message is automatically generated.

> Sentry shell should use kerberos requestor and give better error messages for kerberos failures
> -----------------------------------------------------------------------------------------------
>
>                 Key: SENTRY-1052
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1052
>             Project: Sentry
>          Issue Type: Improvement
>          Components: Service
>    Affects Versions: 1.7.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 1.7.0
>
>         Attachments: SENTRY-1052.patch
>
>
> Currently, the sentry shell uses the java "user.name" which gives some unexpected behavior if the user is logged in via kerberos (i.e. you get error messages about your OS user when connecting to a secure sentry service).
> In addition, the error messages around this are sometimes missing.  For example, for a GSS initiate failure, which happens if there is kerberos ticket, you get no error message returned because the top-level exception has no error message.  We should follow the exception causes until we find something reasonable to print.



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