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

Posted to commits@sentry.apache.org by "Colin Ma (JIRA)" <ji...@apache.org> on 2016/03/22 08:18:25 UTC

[jira] [Assigned] (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:all-tabpanel ]

Colin Ma reassigned SENTRY-1103:
--------------------------------

    Assignee: Colin Ma

> 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: Bug
>            Reporter: Ashish K Singh
>            Assignee: Colin Ma
>
> 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)