"Mike Orr" <[EMAIL PROTECTED]> writes: > We need somebody who has used AuthKit to write the simple HOWTOs that > people are asking for.
I did and did, but it was a while back and I suspect AuthKit's changed since I wrote it: http://pylonshq.com/project/pylonshq/wiki/PylonsWithAuthKitForward I'm using it in a production app for a .gov and a .com client. What bothered me most was that AuthKit wasn't something I could just drop in and start using, with anything beyond the appname.conf file supplying the username/password/groups. I would hope that any sufficiently well-loved auth middleware would ship with some working example apps that (say) stored to an SQLite/MySQL/Postgresql DB, and LDAP/AD, and had user/group/role management forms -- at least for Pylons. It bothered me to have to write these myself, and know that everyone else did too; wasted effort for lazy/efficient programmers. Having said that, I did do an SQLite backend and management forms for the .gov customer, then retrofitted it to get authentication info form a RADIUS server since we use SecurID tokens and that's the easiest protocol with which to communicate with the RSA server. > Regarding auth, that has never been seen as a core Pylons > responsibility. If you want a framework with a built-in auth library, > see TurboGears. I think this approach may scare a lot of people away from Pylons -- I know I would have benefitted from a few more common tools being bundled. > To answer another question in this thread, repoze is a set of > WSGI-compatible libraries spun off from Zope. It's the most > exciting contribution from Zope since ZODB, because it allows Zope > products like Plone and other WSGI apps to be mixed in the same site. > However, it's all brand new so it hasn't been fully evaluated which > parts are most useful in Pylons apps. Again, we need feedback from > people who try repoze.who. At PyCon, I wrote a RADIUS authentication module for repoze.who (with guidance from Chris McDonough). I don't understand the whole stack yet but the approach seems rather good: the plugin was pretty easy to write even tho I had never seen the repoze code before. It would be nice if I could use repoze.who with Pylons, Zope, Grok, and Plone instead of separate auth mechanisms for each. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
