[
https://issues.apache.org/jira/browse/SENTRY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976499#comment-13976499
]
Prasad Mujumdar commented on SENTRY-177:
----------------------------------------
+1
LGTM
> Sentry Policy Service does not treat role names as case insensitive
> -------------------------------------------------------------------
>
> Key: SENTRY-177
> URL: https://issues.apache.org/jira/browse/SENTRY-177
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Lenni Kuff
> Assignee: Sravya Tirukkovalur
> Attachments: SENTRY-177.1.patch
>
>
> The Sentry Policy Service does not treat role names as case insensitive. Role
> names are always stored in lowercase, but the checks to see if a role exists
> are done in a case sensitive fashion. This leads to lots of errors about
> roles not existing when they actually do.
> For example:
> {code}
> SentryPolicyServiceClient client = new SentryPolicyServiceClient(conf);
> Set<String> userGroupNames = Sets.newHashSet();
> userGroupNames.add("lskuff");
> String roleName = "newRole";
> client.createRole("lskuff", userGroupNames, roleName);
> // Fails with role does not exist error message since "newRole" is stored as
> "newrole"
> client.grantRoleToGroup("lskuff", userGroupNames,
> "lskuff", roleName);
> org.apache.sentry.provider.db.SentryNoSuchObjectException: Role:
> TAlterSentryRoleAddGroupsRequest(protocol_version:1,
> requestorUserName:lskuff, requestorGroupNames:[lskuff], roleName:newRole,
> groups:[TSentryGroup(groupName:lskuff)]) does not exist.. Server Stacktrace:
> org.apache.sentry.provider.db.SentryNoSuchObjectException: Role: newRole
> at
> org.apache.sentry.provider.db.service.persistent.SentryStore.alterSentryRoleAddGroups(SentryStore.java:435)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
