aash wrote: > > well, upon further reading i found in the docs the phrase: > > . If you would like to allow the user to view multiple pages without the > need to login first, you will need to implement your own version of > SessionValidator that just returns nothing as a result. > > does anyone have a simple example of this? > > aash > > aash wrote: > > > I was able to get an app to login and move around properly, > > and default back to login when you tried to access a link without > > logging in, or when your password was illegal etc. > > > > (by commenting out screen.login and screen.homepage in TR.props. > > i added a template.login to TR.props. i changed action.sessionvalidator > > > > to sessionvalidator.TemplateSecureSessionValidator (from > > TemplateSessionValidator) This is a good example of a SessionValidators, one requires login the other does not. Security can be implemented a the screen level (as per Jon's response.) You can also implement Security on a finer level (only show the admin link for Admins) following the example from RequireLoginFirst Screen. ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/> Problems?: [EMAIL PROTECTED]
