Furthermore -- there's much better solutions than stand-alone Wikis for what you're trying to do - ranging from FOSS solutions like Moodle or Sakai - to closed-source systems like WebCT or BlackBoard. <disclosure> I used to work for WebCT.</disclosure>
If you insist on staying with a Wiki -- I'd follow Alan's suggestion - look at using Apache authentication or perhaps there's a MoinMoin authnentication module out there. If you're trying to implement SSO between applications - then that's an entirely different problem to solve and is probably OT for this list. Though I'd be happy to talk about your option off-list - if you want to email me at [EMAIL PROTECTED] Mark On 10/1/05, Alan Chandler <[EMAIL PROTECTED]> wrote: > On Saturday 01 Oct 2005 14:18, Todd O'Bryan wrote: > > 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. > > This seems like using an inefficient sledgehammer to crack a nut. > > You don't say what web server you are running MoinMoin on, but I would have > thought that careful use of paths to where each of the wiki's are stored > should allow you to use the appropriate security controls. If you are using > apache, then basic authetication should be sufficient for the stuff you want > and you only need a couple of directives defining the realm and > authentication file for the particular path. > > -- > Alan Chandler > http://www.chandlerfamily.org.uk > > --------------------------------------------------------------------- > 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]
