Support ordering of authentication handlers
-------------------------------------------
Key: SLING-1368
URL: https://issues.apache.org/jira/browse/SLING-1368
Project: Sling
Issue Type: Improvement
Components: Commons
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: Commons Auth 1.0.0
Right now authentication handlers are only ordered by their registration path.
If multiple authentication handlers are registered for the same path, the order
at which they are asked is basically undefined.
It would be useful to be able to control this order using the regular
service.ranking service registration property.
One use of such ordering would be to be able to better control which
authentication handler should be in charge of requesting credentials. For
example, a high priority "pseudo authentication handler" could be provided,
which just renders login forms. Such a provider could provide forms for both
form based authentication and OpenID authentication and support the client in
selecting which form of authentication she/he selects.
Such an authentication handler should of course have precedence in terms of
requesting credentials over the other authentication handlers. Adding support
for service.ranking would solve this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
