[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse

I think the more general point here is why are extensions being used here 
instead of services (which already come built into the OSGi framework) as 
the means of connecting the various players of the JAAS framework? Is 
there something about the JAAS framework design that cannot be done, or 
done well, with services?

Sure one can install the registry (and its dependent bundles) on the OSGi 
framework and use them, but why introduce that coupling unless it truly is 
necessary? I would like to think that we may want to include the JAAS 
framework design in the OSGi spec. But I don't see that OSGi specified 
version of a JAAS framework will be based upon extensions.
-- 

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx

office: +1 386 848 1781
mobile: +1 386 848 3788




Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> 
Sent by: equinox-dev-bounces@xxxxxxxxxxx
2007-09-04 13:48
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc

Subject
Re: AW: [equinox-dev] [sec] JAAS framework dependency on Eclipse






The extension registry is an OSGi bundle, to that respect it runs on any
OSGi implementation.
And for curious, it even runs without OSGi.

PaScaL


  
  From:       "Matt Flaherty" <mwflaher@xxxxxxxxxx>   
  
  To:         Equinox development mailing list <equinox-dev@xxxxxxxxxxx>   
 
  
  Date:       09/04/2007 10:58 AM  
  
  Subject:    Re: AW: [equinox-dev] [sec] JAAS framework dependency on 
Eclipse 
  






In the bug:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=202156

Chris rightly points out that I may have been heavy-handed with 'pure' ;)

Certainly the registry can be used in other environments.. Though I've
never tried it, the framework may very well work if you simply include the
registry. Let me know if there is anything I can do to help get your
environment up and running.

-matt

---
Matt Flaherty
Security Project Lead, Lotus Notes & Eclipse Equinox
External: http://www.eclipse.org/equinox/incubator/security/
Internal: https://cs.opensource.ibm.com/projects/eclipsesec/

equinox-dev-bounces@xxxxxxxxxxx wrote on 09/04/2007 10:11:25 AM:

> That answers my other question as well. Thanks.
>
> I'm going to file a bug right now and will contribute code if I can come
> up with something generic.
>
> I wonder whether the OSGi specification has already hooks available to
> put something like framework wide authentication.
>
> Thanks again and regards
>
> Arthur
>
> Matt Flaherty wrote:
> >
> > The authentication code currently relies on extension points to
> > contribute the JAAS artifacts, so I don't believe it will currently
> work
> > in a pure OSGi environment.
> >
> > Nothing is currently planned in this direction - primarily because no
> > one has asked yet... Requirements (via bugzilla) and contributions are
>
> > both welcome :)
> >
> > ---
> > Matt Flaherty
> > Security Project Lead, Lotus Notes & Eclipse Equinox
> > External: http://www.eclipse.org/equinox/incubator/security/
> > Internal: https://cs.opensource.ibm.com/projects/eclipsesec/
> >
> > equinox-dev-bounces@xxxxxxxxxxx wrote on 09/04/2007 09:33:34 AM:
> >
> >  > Hi all
> >  >
> >  > I'm looking for a way to leverage the authentication functionality
> >  > provided by JAAS for an application running on Equinox (not
> depending on
> >  > the rest of Eclipse). Is it possible to leverage the Equinox
> Security
> >  > framework for this or is it necessary to use the (Eclipse specific)
> >  > extension points it provides to use it? Or are there any plans on
> making
> >  > it a "pure" OSGi bundle?
> >  >
> >  > Regards
> >  >
> >  > Arthur
> >  >
> >  > _______________________________________________
> >  > equinox-dev mailing list
> >  > equinox-dev@xxxxxxxxxxx
> >  > https://dev.eclipse.org/mailman/listinfo/equinox-dev
> >
> >
> >
> ------------------------------------------------------------------------
> >
> > _______________________________________________
> > equinox-dev mailing list
> > equinox-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev