Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAHCW-mnPpSQC5+2_m7WYoLLwXbMYdKPDzuJc0nPCYarkTUa2ww@mail.gmail.com>
References: 
 <CAHCW-mnPpSQC5+2_m7WYoLLwXbMYdKPDzuJc0nPCYarkTUa2ww@mail.gmail.com>
Date: Fri, 28 Sep 2012 01:10:05 +0200
Message-ID: 
 <CALvhUEWA0jUxLhh6kAu5cO_7QN2VwbPwSOJ42oH-=TsaWA75JA@mail.gmail.com>
Subject: Re: Bundle to simplify JAAS usage in OSGi
From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= <reto@apache.org>
To: dev@felix.apache.org
Content-Type: multipart/alternative; boundary=20cf30223c912e73c504cab70a93

--20cf30223c912e73c504cab70a93
Content-Type: text/plain; charset=ISO-8859-1

Hi Chetan

Recently we have added security to Stanbol so that it can be run with a
security manager in place. Regarding authentication of HTTP clients for now
the providers must implement our own service interface [1]. The
authentication providers authenticate a user before subsequent processing
of the request is executed as the authenticated subject.

Could you help me understand what using your bundle would imply. Is this a
regular bundle that can just be added to any OSGi application ore are some
special tweaks needed starting/configuring the platform?

Cheers,
Reto


1.
http://svn.apache.org/viewvc/stanbol/trunk/commons/security/src/main/java/org/apache/stanbol/commons/security/auth/AuthenticationMethod.java?view=markup

On Wed, Sep 26, 2012 at 3:56 PM, Chetan Mehrotra
<chetan.mehrotra@gmail.com>wrote:

> I have been working on a poc to simplify usage if JAAS with Sling and
> Jackrabbit. Using of JAAS within OSGi is often tricky because of
> classloading issues. There has been some work done around this
>
> 1. JAAS support in Apache Karaf
> 2. Proposal by Stefan Vladov in the presentation [1] given by him at
> OSGi Community Event 2011
>
> Following the proposal at #2 and borrowing some ideas from Apache
> Karaf I implemented a bundle which simplifies usage of JAAS within
> OSGi env. It supports following features
>
> 1. It can work both in Standalone and AppServer deployments i.e. in
> those environment where global JAAS configuration might be used by
> other applications and our usage of JAAS should not affect them
> 2. It enables usage of OSGi Configuration support to dynamically
> configure the login modules.
> 3. It allows LoginModule instances to be created via factories
> registered in OSGi Service Registry
> 4. It does not require the client to depend on any OSGi API
> 5. It works well with the dynamic nature of the OSGi env
> 6. Implementation depends only on Core OSGi API and ConfigAdmin
>
> Complete details are provided at [2]
>
> Kindly have a look at it and provide feedback!!
>
> Chetan Mehrotra
>
> [1]
> http://www.slideshare.net/mfrancis/common-security-services-consolidation-patterns-for-legacy-components-stefan-vladov
> [2] https://github.com/chetanmeh/c/wiki/JAAS-in-OSGi
>

--20cf30223c912e73c504cab70a93--