sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-2427) Use Hadoop KerberosName class to derive shortName
Date Tue, 16 Oct 2018 00:14:00 GMT

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

Hadoop QA commented on SENTRY-2427:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12944012/SENTRY-2427.02.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/4179/console

This message is automatically generated.

> Use Hadoop KerberosName class to derive shortName
> -------------------------------------------------
>
>                 Key: SENTRY-2427
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2427
>             Project: Sentry
>          Issue Type: New Feature
>          Components: Sentry
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>         Attachments: SENTRY-2427.01.patch, SENTRY-2427.02.patch
>
>
> Sentry doesn't use auth to local group mapping hadoop configuration. We may have a use
case for cross realm users to have access to sentry service and in which case Sentry needs
to have access to those configurations. Switching to using KerberosName will handle that case
and other cases as well



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message