Hi Les,
Thank you for the prompt reply.
i have been reviewing all Realm implementations , but I am obviously
missing something , since implementing a custom realm only requires
implementing 2 DB queries.
what i don't see , is where does the DB persistence take place , i.e.
persisting new users, roles, groups , permissions; I assume that i need
to implements all of these, by extending existing classes.
do i have to implement my own token, user, account, role, group , etc..?
or are there specific extension point that i can hook into , without
overriding the whole model?
Thanks,
Shay
Les Hazlewood wrote:
Hi Shay,
JSecurity can use any data source - it does that by wrapping access to
that data source in a Realm implementation:
http://www.jsecurity.org/api/org/jsecurity/realm/Realm.html
A Realm is essentially a security-specific DAO, so you can communicate
with any back-end you need. Check out the Sample applications in the
JSecurity distribution, as well as some of the Realm implementations here:
http://svn.apache.org/repos/asf/incubator/jsecurity/trunk/core/src/org/jsecurity/realm/
Look at the text, jndi, ldap sub packages for ideas, as well as the
sample applications that ship with JSecurity's distribution.
I hope that helps!
Cheers,
Les
On Thu, Feb 26, 2009 at 8:53 AM, Shay Matasaro <[email protected]
<mailto:[email protected]>> wrote:
Hi All,
I ran into JSecurity yesterday and it looks very promising, i'd
like to add it to my web service application.
The only hurdle to cross is the fact that my app uses its own
"object oriented DB" ; i would therefore like to customize
Jsecurity to use our own data layer.
is it possible to customize just the low-level db access , and
allow JSecurity to maintain all the great features that it offers
without rewriting all aspects?
if so what is the bare minimum list of objects and interfaces that
i need to extend in order to achieve that goal (this is a new app
, so i don't have to align with any existing table schema).
To the project developers , Great Job! , the library seems very
simple and easy to use, and after messing about with JAAS for
awhile , i can really value simplicity.
Thanks,
Shay
