Authentication/Authorization framework for Openworship

[Scott Guerrieri]

I was looking into the Pylons framework to start developing some of
the controllers for the pages already designed by the group. I have
found that Pylons does not have an Auth mechanism by default. I found
a subproject called AuthKit that was designed to work with Pylons to
deliver this Auth mechanism for any background user/group/permissions
datastore. I wanted to open up the discussion to the group as to
whether this toolkit should be used. What I am looking for is
opinions about the integration with existing user datastores versus a
self contained user datastore specific to openworship. Would it be
worth using AuthKit for its ability to leverage existing datastores or
should we proceed to develop our own "homegrown" mechanism?

[Raoul Snyman]

Hi Scott,

In our IRC and other discussions, I suggested folks look at my Project
HQ project for an auth mechanism. When I started Project HQ I was
excited about AuthKit, and wanted to use it in my project. However,
after gazing at the documentation for ages, I couldn't figure out
exactly how to use it in Project HQ with a database backend.
Eventually, I just rolled my own because it would do exactly what I
wanted.

So... If you can get AuthKit to work for us Scott, then I have no
problems using it, I just couldn't figure out how.

--
Raoul Snyman
B.Tech Information Technology (Software Engineering)
E-Mail: raoul....@gmail.com
Web: http://www.saturnlaboratories.co.za/
Blog: http://blog.saturnlaboratories.co.za/
Mobile: 082 550 3754
Registered Linux User #333298 (http://counter.li.org)