You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Arjun Mishra (JIRA)" <ji...@apache.org> on 2018/10/15 18:40:00 UTC

[jira] [Updated] (SENTRY-2427) Use Hadoop KerberosName class to derive shortName

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

Arjun Mishra updated SENTRY-2427:
---------------------------------
    Description: 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  (was: 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)

> 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
>
> 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)