jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@adobe.com>
Subject Re: Can I use LoginModulePlugins in Oak?
Date Mon, 04 Nov 2013 09:56:05 GMT
hi bertrand

there is no replacement for the repository.xml configuration in OAK;
for neither of the elements mentioned on the jackrabbit configuration

as far as the authentication is concerned the statement wrt JAAS setup is
IMO no longer true. thanks to the effort made by Chetan to incorporate
direct on the Felix level, setting up runtime pluggable authentication
JAAS should no longer be an issue. and writing a LoginModule definitely
be considered difficult.

the separation between 'local' (repository.xml) and JAAS setup in
jackrabbit used to be quite awkward IMO. as far as our products are
concerned i am not aware of any customer making use of that local

are you sure that it is really the configuration part that you are
fighting with?
or are you rather looking for the replacement of the DefaultLoginModule?

kind regards

On 11/4/13 9:59 AM, "Bertrand Delacretaz" <bdelacretaz@apache.org> wrote:

>Hi Angela,
>On Mon, Nov 4, 2013 at 9:53 AM, Angela Schreiber <anchela@adobe.com>
>> ...if i was you i would just deprecate that unfortunate part of sling
>> that intended to make the login module pluggable at runtime and
>> drop it asap....
>Ok, but how do you suggest implementing the use case that's covered by
>Sling's current FormLoginModulePlugin?
>http://jackrabbit.apache.org/jackrabbit-configuration.html says "if
>JAAS authentication is not available or (as is often the case) too
>complex to set up, Jackrabbit allows you to specify a
>repository-specific JAAS LoginModule that is then used for
>authenticating repository users."
>I'm basically looking for the equivalent in Oak, something that a
>Sling instance can setup by default, without requiring users to do any

View raw message