You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/06/11 15:06:46 UTC

[jira] Closed: (SLING-523) Authentication handlers should be configurable for paths

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

Carsten Ziegeler closed SLING-523.
----------------------------------

    Resolution: Fixed

> Authentication handlers should be configurable for paths
> --------------------------------------------------------
>
>                 Key: SLING-523
>                 URL: https://issues.apache.org/jira/browse/SLING-523
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: 2.0.1
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: 2.0.1
>
>
> Currently, all configured authentication handlers are queried one after the other until one of them returns successfully. There is no defined order.
> It would be good to provide support for path based configuration of the handlers. The longest match is tried first in this case.
> If the authentication handler provides a "path" property (non empty), the incomming url must start with this path. If the "path" property is not available or empty, the handler is regarded as inactive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.