[
https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692858#comment-15692858
]
Bertrand Delacretaz commented on SLING-6285:
--------------------------------------------
bq. WDYT about deprecating allowLoginAdministrativeForBundle, so we can later
make it private?
If we do that the only way to implement custom whitelisting logic is to
implement a {{LoginAdminWhitelist}} service, right?.
I think that's good, but we should then provide a way to disable our default
whitelist implementation so that a custom service can replace it - either move
that implementation to its own bundle, make sure service ranking is properly
taken into account when selecting which implementation to use, or use a
configurable OSGi service LDAP filter to select the right implementation.
> Implement LoginAdminWhitelist in JCR Base
> -----------------------------------------
>
> Key: SLING-6285
> URL: https://issues.apache.org/jira/browse/SLING-6285
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Base 2.4.2
> Reporter: Julian Sedding
> Assignee: Julian Sedding
> Fix For: JCR Oak Server 1.1.4, JCR Base 3.0.0
>
> Attachments: SLING-6285-jsedding.patch
>
>
> JCR Base should provide a default implementation
> {{AbstractSlingRepositoryManager#allowLoginAdministrativeForBundle(Bundle)}}
> with a configurable {{LoginAdminWhitelist}}. Implementation that want a
> different logic can then still choose to overwrite the method.
> cc [~cziegeler], [~bdelacretaz]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
