[
https://issues.apache.org/jira/browse/SENTRY-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018154#comment-16018154
]
kalyan kumar kalvagadda commented on SENTRY-1736:
-------------------------------------------------
Older patch had issues as the UserGroupInformation was initialized when the
first connection was created. This will not solve the issue as the connection
is not created when the sentry client is created.
New logic which initialize UserGroupInformation when the first client is
created.
This change set also contains tests to make sure things are as expected.
> Generic service client should support Kerberos
> ----------------------------------------------
>
> Key: SENTRY-1736
> URL: https://issues.apache.org/jira/browse/SENTRY-1736
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: kalyan kumar kalvagadda
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1736.001-sentry-ha-redesign.patch,
> SENTRY-1736.002-sentry-ha-redesign.patch,
> SENTRY-1736.003-sentry-ha-redesign.patch,
> SENTRY-1736.004-sentry-ha-redesign.patch,
> SENTRY-1736.005-sentry-ha-redesign.patch,
> SENTRY-1736.006-sentry-ha-redesign.patch
>
>
> The {{SentryGenericServiceClientDefaultImpl}} has the following comment in
> constructor:
> {code}
> //TODO(kalyan) need to find appropriate place to add it
> // if (kerberos) {
> // // since the client uses hadoop-auth, we need to set kerberos in
> // // hadoop-auth if we plan to use kerberos
> // conf.set(HADOOP_SECURITY_AUTHENTICATION,
> SentryConstants.KERBEROS_MoODE);
> // }
> {code}
> This should be actually implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
