Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of fmeschbe@adobe.com designates
 64.18.1.208 as permitted sender)
From: Felix Meschberger <fmeschbe@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Tue, 19 Feb 2013 10:02:59 +0000
Subject: Re: Time for jackrabbit-jcr-auth?
Thread-Topic: Time for jackrabbit-jcr-auth?
Thread-Index: Ac4OiEv2t0P4QnFmRl+1rzn0LofQoQ==
Message-ID: <3CB20295-CBE2-4003-AA61-CFC179CE23A3@adobe.com>
References: 
 <CAOFYJNbkKA=fEQZka+dUjUy_fBOAi5qKfMycx30k6znokHaMCQ@mail.gmail.com>
In-Reply-To: 
 <CAOFYJNbkKA=fEQZka+dUjUy_fBOAi5qKfMycx30k6znokHaMCQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi

Can you separate API from implementation in the same step ?

Currently API and implementation is "nicely" mixed, which makes it close to=
 impossible to properly use in an OSGi context.

Regards
Felix

Am 19.02.2013 um 10:52 schrieb Jukka Zitting:

> Hi,
>=20
> When looking at the login() code for OAK-634 I realized that there's a
> a lot of duplication between jackrabbit-core and oak-core in this
> area.
>=20
> Would it make sense to split out the authentication code to something
> like jackrabbit-jcr-auth that could be used by both jackrabbit-core
> and oak-core.
>=20
> AFAICT there aren't too many places in the authentication code that
> require deep integration with the repository internals (unlike in
> authorization), so it should be possible to extract the relevant code
> to a separate component. Or am I mistaken?
>=20
> BR,
>=20
> Jukka Zitting


--
Felix Meschberger | Principal Scientist | Adobe