felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4389) Configuration ranking for LMF services should also use "jaas.ranking" property
Date Wed, 22 Jan 2014 07:27:19 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878357#comment-13878357
] 

Felix Meschberger commented on FELIX-4389:
------------------------------------------

Sorry for the dealy and thanks for the patch. I have applied it in Rev. 1560267.

> 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, felix-4389-r1558868.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)

Mime
View raw message