[jifty-devel] authentication plugins

Jesse Vincent jesse at bestpractical.com
Wed Jan 17 13:42:43 EST 2007




On Wed, Jan 17, 2007 at 05:40:31PM +0100, Agostini yves wrote:
> 
> food for thought on authentication plugins

Yves,

Have you had a look at the "plugins 2.0" doc that nelson and I created
in the jifty doc/ directory? It's another design that gets to a lot of
the same ends, I think.

-j

> 
> Actually I don't write any line of code, I need help or advice before
> beginning ;)
> 
> There's 3 main steps :
> 
> 1. add a 'realm' accessor in CurrentUser
> so application can use current_user->realm
> 
> 2. add a User plugin
> in Plugins/Auth/User
> with a default model without action or dispatcher,
> application can override this model.
> We must define this default model.
> 
> 3. add some credential plugins
> 
> in Plugins/Auth/Cred/Ldap
>                     /Cas
>                     /OpenID
>                     /Login
> 
> each credential plugin contains
>  - web pages
> share/web/template/ldaplogin
>                   /ldaplogout
> 
>  - dispatcher
> lib/Jifty/Plugin/Auth/Cred/Ldap/Dispatcher.pm
>  - actions
> lib/Jifty/Plugin/Auth/Cred/Ldap/Action/Login.pm 
> 	which set current_user->id, username and realm
>  ... Logout.pm
> maybe we could use an optional parameter in config.yml to store users in
> User plugin. Sometimes we don't need to register users. 
> 
> 
> Actual Login plugin is now the more complexe plugin
> as people have to confirm their mail address.
> So I think to 2 solutions.
> 1. keep actual model and move confirmed email users to User plugin
> 2. remove model from login plugin and use only User plugin
> 
> 
> What do you think about this ?
> 
> 
> -- 
> Agostini yves <agostini at univ-metz.fr>
> 
> _______________________________________________
> jifty-devel mailing list
> jifty-devel at lists.jifty.org
> http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
> 

-- 


More information about the jifty-devel mailing list