Greetings Pyloneers,
It's be a long time since I hacked something with Pylons but things are moving favorably now. After a flash demo of our great tools, I was able to convince out lead architect that Pylons was the right choice for our next web app. I'm a bit out of sync with the current state of the art so I will need your help as I refine our technological choices. First things first, I need to pick an authentication and authorization solution. Last time I checked, around December, Authkit had a fancy decorator syntax but it was a bit ill documented and featured many strange way of authentication that obscured the most straight forward solution for most people. For that reason, many went the way of rolling they own authentication. Has anything changed since then? I will need to support both basic HTTP authentication for our RESTful API and "forward style" auth for our "human" web interface. Users are going to come from either the application database or from LDAP. It's OK to use PAM as a proxy to LDAP since that generally makes configuration a bit less ugly. (Can we configure auth wiht PAM on MacOS?) I liked Authkit's decorator syntax; if there is anything simple like that, it would be great. That's it, I'm looking for the best auth-and-auth solution that fits the bill and that isn't too painful to setup. If you all tell me that I need to roll my own, I think we are going to hack a reusable authentication package: please tell me what your ideal authentication system would be like. -- Yannick Gingras --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
