You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Ashish K Singh (JIRA)" <ji...@apache.org> on 2016/04/22 22:08:13 UTC
[jira] [Commented] (SENTRY-1103) Authorizable names' case
sensitivity must be decided by plugins
[ https://issues.apache.org/jira/browse/SENTRY-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254569#comment-15254569 ]
Ashish K Singh commented on SENTRY-1103:
----------------------------------------
[~colin_mjj] thanks a lot for taking care of this, would it be possible for you to add some user docs to this, as in how would an integration/ plugin use it? Thanks!
> Authorizable names' case sensitivity must be decided by plugins
> ---------------------------------------------------------------
>
> Key: SENTRY-1103
> URL: https://issues.apache.org/jira/browse/SENTRY-1103
> Project: Sentry
> Issue Type: Sub-task
> Affects Versions: 1.8.0
> Reporter: Ashish K Singh
> Assignee: Colin Ma
> Labels: integration
> Fix For: 1.8.0
>
> Attachments: SENTRY-1103.001-SENTRY-999.patch, SENTRY-1103.002-SENTRY-999.patch
>
>
> With more and more components relying on sentry for authorization, it really makes sense to have the case-sensitivity configurable. We can keep the current behavior as default. However, for use cases like Kafka, it makes sense to have authorizable names case sensitive. For instance, a topic resource in Kafka can have case sensitive values, like, topic1 and TOPIC1 are two completely different valid topic resource instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)