Hi JB thanks for the so quick answer.
Yes you are right my plans are tro write another LoginModule but without
being tied with Karaf.
Just to ensure my vision is right, there 's no hidden beast involved with
JAAS beyonh the realm/principal and loginmodule classes ?
Kind regards
Jerome
On Mon, Jun 6, 2016 at 9:47 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:
> Hi Jerome,
>
> yes extending OsgiConfigLoginModule can do the trick.
>
> Or even more generic, you can directly implement a regular LoginModule (as
> we do in Jdbc, LDAP, Properties login module).
>
> Another possible way is to leverage the Syncope login module.
>
> Anyway, what you are doing looks like the PropertiesLoginModule which
> deals with users stored in properties files (with password, encrypted or
> not).
>
> Regards
> JB
>
>
> On 06/06/2016 09:06 AM, jerome moliere wrote:
>
>> Hi all,
>> It may be quite unusual here but I'd like you to help to drop some
>> strong project 's dependencies with Karaf and especially with the JAAS
>> related classes.
>> We use some Karaf classes to manage JAAS security features in our
>> application and I an aked to cut off these dependencies.
>> In our code in can find :
>> karaf Principal classes
>> Encryption* classes
>> and configuration using the LoginModule for retrieving users from
>> properties file (encrypted)
>>
>> I can quickly create our own Principal classes ( 10 minutes), I can use
>> whatever JCE classes to get the cryptographic features there's no
>> problem with that point too.
>>
>> I would like to check one point: most of the job in the JAAS specific
>> code in Karaf is done through the OsgiConfigLoginModule isn't it ? So
>> creating a new class would make the trick isn't it?
>>
>> Is there any important element to be migated for getting a functional
>> JAAS application?
>>
>> Thanks for your help
>> Kind regards
>> Jerome
>>
>> --
>> J.MOLIERE - Mentor/J
>>
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
--
J.MOLIERE - Mentor/J