jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8045) Allow for ranking being specified with UserAuthenticatonFactory implementations
Date Tue, 02 Apr 2019 09:29:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807585#comment-16807585

angela commented on OAK-8045:

[~stillalex], i had a chat with [~cziegeler] this morning and he suggested to use {{ServiceReference}}
as the second parameter in the bind method and subsequently use it as key in the sorted map
as it implements {{Comparable}} respecting service ranking and service id.
will attach an initial proposal for a patch and also try to come up with a test... once have
an approach we feel comfortable with I would suggest we create a separate issue to address
the same problem with the other lists kept in {{SecurityProviderRegistration}}.

> Allow for ranking being specified with UserAuthenticatonFactory implementations
> -------------------------------------------------------------------------------
>                 Key: OAK-8045
>                 URL: https://issues.apache.org/jira/browse/OAK-8045
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, security-spi
>            Reporter: angela
>            Priority: Major
> Currently the {{SecurityProviderRegistration}} lists {{UserAuthenticationFactory}} implementions
according to the order they are bound. While other parts of the security setup (e.g. AuthorizationConfiguration)
allow for an explicit ranking to be specified this option is missing with {{UserAuthenticationFactory}}
as reported in the following thread on jackrabbit-users: https://markmail.org/message/hieqxfdvsadi3lyr
> [~stillalex], wdyt?

This message was sent by Atlassian JIRA

View raw message