Application agents: Difference between revisions

From RavenWiki
Jump to navigationJump to search
No edit summary
No edit summary
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{New Docs}}
{{Raven Legacy}}
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.
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.
 
This is a pseudo-code example of how an Application Agent might be
implemented:
[[Pseudo-code_Application_Agent]]
[[Pseudo-code_Application_Agent]]



Latest revision as of 11:46, 3 March 2020

We're working on improving Raven resources for developers and site operators.

Try out the new Raven documentation for size.

The WebAuth protocol should not be used for new sites or applications.

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. This is a pseudo-code example of how an Application Agent might be implemented: Pseudo-code_Application_Agent

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 University Information Services

Provided by the University Information Services

... but not officially supported

Provided by others