Application agents: Difference between revisions
From RavenWiki
Jump to navigationJump to search
(Ass suggestion of posting to cs-raven-announce) |
m (Fix typo) |
||
Line 3: | Line 3: | ||
Application Agents are available for various platforms and with varying levels of support. | 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 [mailto:cs-raven-announce@lists.cam.ac.uk cs-raven-announce@lists.cam.ac.uk] - it's a moderated list but | If you add something new here you might want to send a short announcement to [mailto:cs-raven-announce@lists.cam.ac.uk cs-raven-announce@lists.cam.ac.uk] - it's a moderated list but relevant posts will be approved. | ||
==Suported by the Computing Service== | ==Suported by the Computing Service== |
Revision as of 12:44, 2 December 2005
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.
Suported by the Computing Service
- Apache authentication module (for Apache 1 and Apache 2) ( Debian package available)
- Raven Java Toolkit
Provided by the Computing Service
... but not officially supported
Provided by others
- Tomcat authenticator and JAAS implementation
- Tomcat Valve
- Ruby Support (including CGI, Webrick and Ruby on Rails)
- JAVA Servlet Library
- Python