You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2018/10/23 01:30:00 UTC
[jira] [Commented] (SENTRY-2432) The case of a username is ignored
when determining object ownership
[ https://issues.apache.org/jira/browse/SENTRY-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659909#comment-16659909 ]
Hadoop QA commented on SENTRY-2432:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12945112/SENTRY-2432.001.patch against master.
{color:red}Overall:{color} -1 due to 4 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA
{color:red}ERROR:{color} Failed: org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/4194/console
This message is automatically generated.
> The case of a username is ignored when determining object ownership
> -------------------------------------------------------------------
>
> Key: SENTRY-2432
> URL: https://issues.apache.org/jira/browse/SENTRY-2432
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Na Li
> Assignee: Na Li
> Priority: Major
> Attachments: SENTRY-2432.001.patch
>
>
> Sentry saves user name associated with a privilege in lower case. And when getting privileges of a given user, the query returns the privileges associated with a user in case-insensitive way.
> Therefore, if there are two users, only differ in case, will have same privileges.
> For example:
> 1) User user_1 is granted privilege "ALL" on a database DB_1
> 2) then User USER_1 has full access on that database,
> The desired behavior is to keep user name case sensitive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)