(potential) Code of Practice for "systems" using Raven: Difference between revisions

From RavenWiki
Jump to navigationJump to search
(first draft of code of practice added)
(No difference)

Revision as of 15:35, 19 December 2005

It would be very useful if administrators of any system (NOTE: not simply webpages) that has a web-interface and chooses to use Raven for authentication follow a simple code of practice that means they voluntarily:

1) Tell the UCS (via cs-hdadmin@lists or maybe raven-support@ucs ?) and give us email/phone/webpage-URL/location of their support contact point so we could maintain a list (preferably on the web) of known systems that use RAVEN & how to contact them. A bit like External Contact Points.

2) Has a sensible webpage that gives the above to users who have sucessfully RAVEN authenicated but can't access the system (e.g. no account). {NOTE: Even CamSIS only gives: "CamSIS account details are invalid. Please contact the CamSIS Helpdesk to resolve or... Return to CamSIS Sign In". At least it says "CamSIS Helpdesk" but it doesn't say how!)

3) Has a clear "System Unavailable until XXX due to maintenance" message if the back-end system is not available.