On Fri, Sep 28, 2012 at 12:33 AM, Marcel Offermans < [email protected]> wrote:
> Judging from his original mail, Chetan seems to already be aware that > there is an implementation in Karaf. I would be interested in hearing what > the differences with the Karaf implementation are. I don't mind multiple > implementations, that's what OSGi is all about, as long as those > implementations have "unique features" that allow you to use them in > situations where the other implementations work less well. > > You're right, I read the original email too quickly. Interesting. The new ConfigurationSpi object has definitely opened some doors with JDK 6. It's a shame we still need to put the ProxyLoginModule in the boot classpath though. I was hoping we could get rid of that. > So perhaps Chetan can explain a bit more about this. > > In general I am positive towards anybody contributing and maintaining new > functionality. > Of course. I really should have read the email more carefully ... > > Greetings, Marcel > > On Sep 28, 2012, at 0:01 AM, Guillaume Nodet <[email protected]> wrote: > > > Fwiw, Karaf already has full JAAS support in OSGi, so it might be worth > > looking at it instead of rewriting the wheel. > > https://github.com/apache/karaf/tree/karaf-2.3.x/jaas > > > > On Thu, Sep 27, 2012 at 11:47 PM, Felix Meschberger <[email protected] > >wrote: > > > >> Hi, > >> > >> Thanks Chetan for the proposal. > >> > >> I find this a very interesting project and would think it would be a > good > >> addition to the Apache Felix portfolio. > >> > >> What do others think ? > >> > >> Disclosure: Chetan also works for Adobe and we have been discussing this > >> before. > >> > >> Regards > >> Felix > >> > >> Am 26.09.2012 um 15:56 schrieb Chetan Mehrotra: > >> > >>> 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 > >> > >> > > > > > > -- > > ------------------------ > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > ------------------------ > > FuseSource, Integration everywhere > > http://fusesource.com > > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
