|
| SeedUserAuthentication |
UserPreferences |
| SEED Wiki | FrontPage | RecentChanges | TitleIndex | WordIndex | SiteNavigation | HelpContents |
Notes on adding user authentication and tracking for NMPDR work.
The Sprout/NMPDR environment relies upon some sort of user authentication in order to tag annotations made by that user, and for access control
We also anticipate using such a user authentication mechanism in the SEED for more sophisticated access control (for protecting against unauthorized updates to a SEED server, or for subsystem write access, etc).
The authentication system has the following components.
An authentication database maintains records of user accounts. A user can be a member of zero or more groups. It is anticipated that group membership will be used for authorizing access to protected resources.
Any CGI code that accesses such resources, or that needs to know about user information (for the purposes of accessing user preferences, for instance) will need to authenticate the user against the authentication database. This authentication is performed using HTTP cookies used to maintain session state, via the CGI::Builder::Auth mechanism (for a start anyway).
