[
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.
