On Sep 22, 2006, at 5:32 PM, Jorge Vargas wrote: > Right now there are two possible solutions. > > 1- Implement identity providers based on RuleDispacher and peak > security you can find this at ticket #313 > 2- Implement identity providers as a set of subclasses.
Actually, there are a couple more. 3. Use Alberto's TurboPeakSecurity (somehow mushed in with our identity APIs for backwards compatibility) (which is similar in idea to #313) 4. Use a WSGI auth provider I don't want to get too much into implementation details on this list (those belong on the trunk list), but this is a fine place to discuss the needs. The biggest need I see is that we need to disambiguate the authentication and authorization. They are two separate tasks that would likely need different plugins. The ideal would probably be some hybrid approach... starting with a WSGI provider, but possibly making an authorization plugin that uses RuleDispatch. As always, I'm looking to leverage as much good stuff that's out there as we can. I know that James Gardner has something up his sleeve, but he mentioned that it's not ready for a big audience yet. Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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 -~----------~----~----~----~------~----~------~--~---
