I can only speak from my experience with 2.0 and earlier (we haven't upgraded, yet...,) but changing the security model to use your own user-auth is not trivial, but not impossible. You have to rewrite the security service (both the service & the UserManager in org.apache.turbine.services.security.db) to use your schema/peers (and of course update TR.props).
As for trying to change the User interface to use your own, I don't know, but I'm guessing it would ripple like the dickens... Any more current developers have a comment??? Steve -----Original Message----- From: Mark Kaye [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 13, 2002 9:43 AM To: [EMAIL PROTECTED] Subject: Newbie: Architecture question 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]>
