Design Specs: Authorization and Authentication

Objectives

This element will need to work with the core code of the web application to implement user authorization and authentication. Catalyst has great support for this already, but we will also need to build a user database for enabling greater customizability.

Is customization mainly for GBrowse? Are there any data that should not be available to public?

=1. Users will be able to create new accounts, or log in to the system using an Open ID =2. User preferences will be stored in a back-end database...

Gbrowse Compatibility

look into Gbrowse2 user registration and login system

To Explore

Catalyst::Plugin::Authentication

http://search.cpan.org/~flora/Catalyst-Plugin-Authentication-0.10016/lib/Catalyst/Plugin/Authentication.pm

And for Credential verification:

http://search.cpan.org/perldoc?Catalyst%3A%3AAuthentication%3A%3ACredential%3A%3AOpenID

Here are some docs on Auth/Auth:

http://search.cpan.org/perldoc?Catalyst::Manual::Tutorial::05_Authentication

Catalyst Tutorial on Authentication: http://www.catalystframework.org/calendar/2008/19

This module might also be useful:

Catalyst::Extension::SimpleLogin