I need to force a Turbine app to forget about checking
the user against the Turbine DB; in fact, the user will
NOT exist in that DB, and it will be validated by an
external process. To accomplish this, I plan to change
the SessionValidator to do basically this:
public class MySessionValidator extends TemplateSessionValidator
{
public void doPerform( RunData data ) throws Exception
{
data.setUser(TurbineSecurity.getAnonymousUser());
data.save();
}
}
Is this the right approach? Can anybody point any potential
pitfalls with this approach?
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
