hi felix
as explained in my reply to jukka the oak authentication doesn't
make use of JCR API but only uses OAK API and some additional
oak level pluggins.
you may want to follow OAK-608 that covers runtime pluggability
of the authentication setup as well as the various subtasks of
OAK-17 for the various other security related APIs that have
to be pluggable.
just yesterday i fixed an bug in the commit-hook setup (they
used to be immutable after the initial repo-setup) in order
to assert that runtime changes to the security modules get
reflect in the commit hook(s) as well... in other words: not yet
there but take for granted that it's not going to be left out
this time :-)
regards
angela
On 2/19/13 11:21 AM, Felix Meschberger wrote:
Hi,
If that's all, that is required, I am fine.
Regards
Felix
PS: DefaultLoginModule uses SessionImpl, NodeImpl, and UserImpl. That would
have to be fixed, I would assume ?
Am 19.02.2013 um 11:08 schrieb Jukka Zitting:
Hi,
On Tue, Feb 19, 2013 at 12:02 PM, Felix Meschberger<[email protected]> wrote:
Can you separate API from implementation in the same step ?
The way I see it, the APIs used by such a component should ultimately
be just JAAS and JCR.
BR,
Jukka Zitting
--
Felix Meschberger | Principal Scientist | Adobe
