You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2014/01/15 20:23:50 UTC
[jira] [Updated] (FELIX-4389) Configuration ranking for LMF
services should also use "jaas.ranking" property
[ https://issues.apache.org/jira/browse/FELIX-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tobias Bocanegra updated FELIX-4389:
------------------------------------
Attachment: felix-4389-r1558508.patch
patch containing the suggested changes
> 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
> 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)