[jira] [Resolved] (FELIX-4389) Configuration ranking for LMF services should also use "jaas.ranking" property

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger resolved FELIX-4389.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: jaas-0.0.2

Thanks for providing the patch.

I have applied it with a small extension in Rev. 1558854:
   - For backwards compatibility support for service.ranking is retained
       if the jaas.ranking property is missing
   - Also consolidated the service property and configuration constants

> Configuration ranking for LMF services should also use "jaas.ranking" property
> ------------------------------------------------------------------------------
>
>                 Key: FELIX-4389
>                 URL: https://issues.apache.org/jira/browse/FELIX-4389
>             Project: Felix
>          Issue Type: Improvement
>          Components: JAAS
>    Affects Versions: jaas-0.0.2
>            Reporter: Tobias Bocanegra
>            Assignee: Felix Meschberger
>             Fix For: jaas-0.0.2
>
>         Attachments: felix-4389-r1558508.patch
>
>
> The JAAS configuration entries that are managed by configuration are sorted using the "jaas.ranking" property, but the entries that are managed via a LoginModuleFactory service are ranked using the "service.ranking" property.
> this might be a problem if an implementing class also implements another service that is ranked by the "service.ranking" property (e.g. the AuthenticationHandlers in Sling).
> Suggest to use the "jaas.ranking" also for LMF service based entries.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)