[jira] [Updated] (SLING-3245) TenantAdapterFactory can return incorrect 'null' tenants depending on order of pathMatchers

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikas Saurabh updated SLING-3245:
---------------------------------

    Attachment: fix_early_tenantQuery_exit.patch

patch for the fix of the issue

> TenantAdapterFactory can return incorrect 'null' tenants depending on order of pathMatchers
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-3245
>                 URL: https://issues.apache.org/jira/browse/SLING-3245
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Tenant 1.0.0
>            Reporter: Vikas Saurabh
>            Priority: Minor
>         Attachments: fix_early_tenantQuery_exit.patch
>
>
> For a case where users under /home/users/abc/tenant_name/ with an existing tenant tenant_name (assuming pathMatchers have a correct regex to be matched) should be identified with correct tenant without relying on order of entries in pathMatchers.
> * Of course, the assumption is that pathMatchers can match a tenant name uniquely
> * e.g. pathMathers={"/home/users/([^/]+)/*", "/home/users/abc/([^/]+)/*} should work



--
This message was sent by Atlassian JIRA
(v6.1#6144)