Personally I think that writing custom plugins for repoze.who is infinitely easier than for the old Identity/Visit system, but that's just my opinion. Anyway I just thought I would give you some examples to run on, Diez, since I had to do exactly the same thing last week :)
My code is incredibly alpha right now, but here's a copy of my middleware.py, which has the custom plugins defined inside. http://paste.turbogears.org/paste/3287 These plugins work with a library I've written to interact with a goofy authentication system written in PHP. It's a little hard to follow, but all the base library does is pull XML resources based on a few different keys that are set in the configuration. If you have any questions about how my plugins actually work, I'd be more than happy to answer them to the best of my ability. To deactivate the SQLAlchemy identity stuff, all you have to do is change base_config.auth_backend to something else, personally I set this to correspond to my plugins for our auth system. From there you can create a new variable in base_config and set it equal to a new Bunch. Honestly I want to thank the TurboGears and repoze.who guys for building and integrating this awesome authorization and authentication system into the framework. So, thanks guys :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
