Raven-enabled applications: Difference between revisions
From RavenWiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 180: | Line 180: | ||
<tr> | <tr> | ||
<td>[https://www.djangoproject.com/ Django]</td> | <td>[https://www.djangoproject.com/ Django]</td> | ||
<td>[https://git.csx.cam.ac.uk/x/ucs/raven/django-ucamwebauth.git django-ucamwebauth]</td> | <td>[https://git.csx.cam.ac.uk/x/ucs/raven/django-ucamwebauth.git django-ucamwebauth] (Documentation for the [[Django]] module)</td> | ||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
Revision as of 14:16, 22 September 2014
Details of applications that have or could be adapted to use Raven, via either the Ucam-Webauth protocol or Shibboleth. Note that this list is bound to be incomplete - before doing significant work on something not listed here (or perhaps even on something that is) it might be worth asking on the cs-raven-discuss@lists.cam.ac.uk mailing list and/or public Shibboleth support lists.
Just because there is something listed under 'Ucam WebAuth' or 'Shibboleth' doesn't imply that support for these protocols exists or is known to be working! Details of support for 'competing' technologies are included since they often provide useful hints about how Raven support could be implemented.
Custom Raven applications
Applications written directly to use Raven:
- Crow - Raven intermediary
- CamCORS
- Room Booking
- WebNAG, a Raven-based replacement for NoCat
- Lapnet, a locally written captive portal (wired only atm!)
