Application agents: Difference between revisions
From RavenWiki
Jump to navigationJump to search
(→Supported by the [[inst:CS | Computing Service]]: 2.2 looks to be stable) |
(Add pms52's servlet filter) |
||
| Line 20: | Line 20: | ||
* [[PHP library]] | * [[PHP library]] | ||
* [[Crow - Raven intermediary]] | * [[Crow - Raven intermediary]] | ||
* [[Servlet filter]] | |||
* [[Apache lookup module]]: Not really Raven, but expected to be used in conjunction with Raven. This will become supported once we have more experience with it. | * [[Apache lookup module]]: Not really Raven, but expected to be used in conjunction with Raven. This will become supported once we have more experience with it. | ||
Revision as of 09:59, 30 August 2007
To use Raven authentication on a webserver you need to implement a 'Application Agent'. This could be built-in to a web application (such as a CGI script or a PHP program), or it could be an 'Authentication handler' for the webserver that you are using.
Application Agents are available for various platforms and with varying levels of support.
If you add something new here you might want to send a short announcement to cs-raven-announce@lists.cam.ac.uk - it's a moderated list but relevant posts will be approved.
Supported by the Computing Service
- Apache authentication module (for Apache 1.3, 2.0 and 2.2)
- Windows IIS authentication module (for IIS V6)
- Raven Java Toolkit
Provided by the Computing Service
... but not officially supported
- Apache lookup module: Not really Raven, but expected to be used in conjunction with Raven. This will become supported once we have more experience with it.
Provided by others
- Tomcat authenticator and JAAS implementation
- Tomcat Valve
- Ruby Support (including CGI, Webrick and Ruby on Rails)
- JAVA Servlet Library
- Python
- Catalyst
- Drupal
- Coldfusion
