Differences between revisions 1 and 2
Revision 1 as of 2005-01-21 03:14:19
Size: 1626
Editor: CPE-61-9-201-26
Comment: Migrated page.
Revision 2 as of 2009-09-20 22:00:11
Size: 1626
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Turbine 2.x User's Guide: Not Using Turbine Security

If you are using Turbine only for a MVC framework, and are not trying to use the built in security features, then you need to do a couple things to make Turbine happy. Turbine requires an Anonymous user to be available, however, if you never try and save that Anonymous user, then the fact that there is no persistent data store (a user database) is fine. To configure things, set these values in your TurbineResources.properties:

Use the default security service


Make sure you aren't trying to persist any users

services.SecurityService.user.manager = org.apache.turbine.services.security.passive.PassiveUserManager

You will still be able to do things like:

 User user = data.getUser() 
 user.setTemp("myval","something to store");

but you will always be working with an anonymous user!

One more note. If you use the PassiveUserManager, you cannot use any of the secure Screen or Action classes that ship with Turbine because you have no way of logging a user in. For an essentially insecure app, this is fine however. And if you wish to use your own security implementation, you can easily create your own secure Screen and Action class hierarchy.

Also, this does not remove your dependency on the Torque and Village jar files. You still need those in your lib dir. Until the turbine User object is fully abstracted from torque, this will continue to be the case.

Turbine2/UsersGuide/TurbineSecurityNotUsing (last edited 2009-09-20 22:00:11 by localhost)