You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Rory Douglas (JIRA)" <ji...@apache.org> on 2009/02/03 20:47:59 UTC

[jira] Created: (SLING-849) Enhance SlingAuthenticator's handler selection mechanism

Enhance SlingAuthenticator's handler selection mechanism
--------------------------------------------------------

                 Key: SLING-849
                 URL: https://issues.apache.org/jira/browse/SLING-849
             Project: Sling
          Issue Type: Improvement
          Components: Engine
    Affects Versions: Engine 2.0.2
            Reporter: Rory Douglas
            Priority: Minor


Currently, AuthenticationHandlers can only be registered by path.  It would be useful to be able to register them with additional attributes, in particular hostname, to enable different authentication mechanisms for different virtual hosts.  It may also be useful to indicate a priority, for ordering purposes when 2 or more handlers are registered for the same set of attributes (path, hostname etc).

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


[jira] Updated: (SLING-849) Enhance SlingAuthenticator's handler selection mechanism

Posted by "Rory Douglas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rory Douglas updated SLING-849:
-------------------------------

    Attachment: SlingAuthenticator.java

I've extended the current AuthenticationHandler.PATH property processing to include handling of hostname and protocol.  Only the SlingAuthenticator is affected by this change.  Existing path registrations (starting with '/') will work as-is.

New mappings are possible:
//hostname
//hostname:port
//hostname/path
http://hostname
https://hostname:port/path
etc

> Enhance SlingAuthenticator's handler selection mechanism
> --------------------------------------------------------
>
>                 Key: SLING-849
>                 URL: https://issues.apache.org/jira/browse/SLING-849
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.2
>            Reporter: Rory Douglas
>            Priority: Minor
>         Attachments: SlingAuthenticator.java
>
>
> Currently, AuthenticationHandlers can only be registered by path.  It would be useful to be able to register them with additional attributes, in particular hostname, to enable different authentication mechanisms for different virtual hosts.  It may also be useful to indicate a priority, for ordering purposes when 2 or more handlers are registered for the same set of attributes (path, hostname etc).

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


[jira] Resolved: (SLING-849) Enhance SlingAuthenticator's handler selection mechanism

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger resolved SLING-849.
-------------------------------------

    Resolution: Fixed

Resolving this issue for now. If we need some more work for ordering (mabye leveraging the standard service.ranking property), we should create a new one.

> Enhance SlingAuthenticator's handler selection mechanism
> --------------------------------------------------------
>
>                 Key: SLING-849
>                 URL: https://issues.apache.org/jira/browse/SLING-849
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.2
>            Reporter: Rory Douglas
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: Engine 2.0.4
>
>         Attachments: SlingAuthenticator.java
>
>
> Currently, AuthenticationHandlers can only be registered by path.  It would be useful to be able to register them with additional attributes, in particular hostname, to enable different authentication mechanisms for different virtual hosts.  It may also be useful to indicate a priority, for ordering purposes when 2 or more handlers are registered for the same set of attributes (path, hostname etc).

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


[jira] Commented: (SLING-849) Enhance SlingAuthenticator's handler selection mechanism

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SLING-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671687#action_12671687 ] 

Felix Meschberger commented on SLING-849:
-----------------------------------------

Thanks for the patch. I have applied it in Rev. 742179.

Will you provide another patch for the ordering priority ? Otherwise we might close this issue and create another one later.

> Enhance SlingAuthenticator's handler selection mechanism
> --------------------------------------------------------
>
>                 Key: SLING-849
>                 URL: https://issues.apache.org/jira/browse/SLING-849
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.2
>            Reporter: Rory Douglas
>            Priority: Minor
>             Fix For: Engine 2.0.4
>
>         Attachments: SlingAuthenticator.java
>
>
> Currently, AuthenticationHandlers can only be registered by path.  It would be useful to be able to register them with additional attributes, in particular hostname, to enable different authentication mechanisms for different virtual hosts.  It may also be useful to indicate a priority, for ordering purposes when 2 or more handlers are registered for the same set of attributes (path, hostname etc).

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


[jira] Updated: (SLING-849) Enhance SlingAuthenticator's handler selection mechanism

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-849:
------------------------------------

    Fix Version/s: Engine 2.0.4
         Assignee: Felix Meschberger

> Enhance SlingAuthenticator's handler selection mechanism
> --------------------------------------------------------
>
>                 Key: SLING-849
>                 URL: https://issues.apache.org/jira/browse/SLING-849
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.2
>            Reporter: Rory Douglas
>            Assignee: Felix Meschberger
>            Priority: Minor
>             Fix For: Engine 2.0.4
>
>         Attachments: SlingAuthenticator.java
>
>
> Currently, AuthenticationHandlers can only be registered by path.  It would be useful to be able to register them with additional attributes, in particular hostname, to enable different authentication mechanisms for different virtual hosts.  It may also be useful to indicate a priority, for ordering purposes when 2 or more handlers are registered for the same set of attributes (path, hostname etc).

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