map the application servlet to everything:
<servlet>
<servlet-name>app</servlet-name>
<servlet-class>org.apache.tapestry.ApplicationServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>app</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
in T4:
implement a filter:
public class SecurityFilter implements ServletRequestServicerFilter
{
// authenticate etc.
}
regards
Peter
-----Ursprüngliche Nachricht-----
Von: Todd O'Bryan [mailto:[EMAIL PROTECTED]
Gesendet: Samstag, 1. Oktober 2005 15:18
An: Tapestry users
Betreff: Use Tapestry to control access to non-Tapestry pages
I'm trying to set up some Wikis on the school server I administer,
but I'd like them to only be accessible to the people they're
concerned with. (For example, if a world history class sets up a wiki
where they can share notes, have discussions, etc., there's no reason
that the people taking US History should ever go to it, and there's
less likelihood I'll get obnoxious posts if viewing/editing/etc is
limited to people who should care about it.)
Is there a way to have Tapestry intercept requests for pages that
aren't controlled by the Tapestry app itself and act as a security
gateway, allowing requests from users who have logged in
appropriately (and serving the appropriate page from the wiki
engine), but blocking unwanted access?
I'm using MoinMoin and apparently you can create a SecurityPolicy
class in Python, so maybe it could talk to the Tapestry app and work
things out that way.
Any ideas of what would be the easiest/best way to do this?
Thanks,
Todd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
