You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Paul Hunter <pa...@apsolve.com> on 2003/10/21 13:24:27 UTC

Secure screens

Hi,

I have an application which is now not functioning correctly.

It appears to not find/execute any of the screens/classes when I request a template(.vm file) from the browser.  It also doesnt find any actions.

I made a change to the SecureScreen class to allow all users access, rebult, which worked (resulting in users no longer having to login).  I then had to go back to the previous implementation where I wanted users to login before seeing the screens.  However after rebuilding it does not forward to the login screen.   I have done a clean prior to rebuilding.   I do not believe I changed any properties.

Can anyone suggest a cause?

Thanks

Paul Hunter
email:paul.hunter@apsolve.com

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org


RE: Secure screens

Posted by Greg Kerdemelidis <gk...@snap.net.nz>.
What is the behaviour of the webapp now when you request templates? Does it
complain that it cannot find that action/template/screen class (with a fat
stack trace) or does it simply render something else?

Things to watch for:

* module.packages property in the WEB-INF/conf/TurbineResources.props file.
Make sure you've got your top-level modules package listed here. If this is
missing, you'll get stack traces complaining about not finding the template.

* isAuthorized() method in the *Screen subclasses (eg, SecureScreen). Bear
in mind the difference between different user "types" -- anonymous user,
not-logged-in, and an authenticated user. Really basic checking can be done
with data.getUserFromSession().hasLoggedIn(), rather than matching against
ACLs. If your isAuthorized() is broken, you've got problems.

* In your isAuthorized() method, if the user fails the auth check, do a
data.setScreenTemplate("Login.vm") to point them back to the login page (or
whatever). If this is missing, failed auth checks will not redirect to the
login page. I'll put $2 on this.

Regards,

Greg Kerdemelidis
Genix Systems Ltd
http://www.genixsystems.com/


> -----Original Message-----
> From: Paul Hunter [mailto:paul.hunter@apsolve.com]
> Sent: Wednesday, 22 October 2003 12:24 a.m.
> To: Turbine Users List
> Subject: Secure screens
> 
> Hi,
> 
> I have an application which is now not functioning correctly.
> 
> It appears to not find/execute any of the screens/classes when I request a
> template(.vm file) from the browser.  It also doesnt find any actions.
> 
> I made a change to the SecureScreen class to allow all users access,
> rebult, which worked (resulting in users no longer having to login).  I
> then had to go back to the previous implementation where I wanted users to
> login before seeing the screens.  However after rebuilding it does not
> forward to the login screen.   I have done a clean prior to rebuilding.
> I do not believe I changed any properties.
> 
> Can anyone suggest a cause?
> 
> Thanks
> 
> Paul Hunter
> email:paul.hunter@apsolve.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org