Thanks Jean-Baptiste,
So then I should do all JAAS configuration from Karaf, right?
The application has its own JAAS LoginModule in the non-OSGI codebase
so would it be something like this? :
<blueprint ...>
...
<jaas:config name="karaf" rank="1">
<jaas:module className="org.apache...PropertiesLoginModule"/>
</jaas:config>
<jaas:config name="myjaas" rank="1">
<jaas:module className="MyJaasLoginModule"/>
</jaas:config>
</blueprint>
Should I use bootdelegation or packages.extra to make OSGI find my
non-OSGI LoginModule?
Best regards
Mike
Jean-Baptiste Onofré wrote:
> Hi Mike,
>
> my advice is to use the JAAS/Security framework provided by
> Karaf. You
> can create your own realms, using different login modules (including
> your own modules).
>
> This framework is available as an OSGi service, and can be
> injected in
> your application.
>
> Regards
> JB
>
> On 11/30/2012 02:28 AM, Mike Wilson wrote:
> > We are embedding Karaf within an existing application which
> > is using JAAS for user login handling. As we want to use
> > the Karaf console as well, we need to have JAAS available
> > both in the existing application's "static" code, and in
> > the OSGI container.
> >
> > How is this best set up?
> > - let application refer to JAAS service in OSGI
> > - or, let OSGI refer to statically loaded JAAS in application
> > - or, somehow load two independent JAAS implementations
> > ?
> >
> > Thanks
> > Mike Wilson
> >
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
