Scarab, scarab.tigris.org, uses turbine's security system, and uses its own table/object to implement the group interface. You might use that as an example, though in your case you would be doing a similar thing for the user table. Scarab is also built so that it can use other security implementations.
john mcnally Mark Kaye wrote: > > I am looking at using Turbine as the framework for my application. We > already have designed a database schema for the application which > incorporates user authentication data, etc. We have the concept of an > individualID which is a primary key on the core user table (individuals) > and a foreign key on several related tables (addresses, logins, > individual_type), etc. Now I come to look at Turbine I see it has its > own user-auth mechanism. > > Will it be easy for me to integrate these or should I build my own auth > mechanism into the Turbine framework from scratch? Sorry if this sounds > a simple question - I'm just getting into Turbine. Any advice you can > give would be much appreciated. > > Best, > > M > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
