That would be a good reason to use r.who in this case, sure. Of course, if you don't have enough control when you use r.who, you can always take the code "internal" if you need to by creating a BFG authentication policy based on the code from these plugins.
Tim Hoffman wrote: > Hi Chris > > On the face of it then , I will probably do the work as plugins to > repoze.who as it seems there are a few repoze.who plugins > already in existence for OAuth , openid, facebook connect etc.... that > I can hopefully leverage off. > > Cheers > > T > > On Mon, Jan 25, 2010 at 6:46 PM, Chris McDonough <chr...@plope.com> wrote: >> I don't think it makes much of a difference if you need to write it all from >> scratch anyway. Either would be fine. >> >> - C >> >> Tim Hoffman wrote: >>> Hi Folks >>> >>> I am looking for some advice. >>> >>> I need to be able to use multiple authentication sources for a new >>> repoze.bfg based app. Do you think I should should use repoze.who >>> etc... >>> or try and hook the various auth directly under bfg's existing >>> authenctication model ? >>> >>> Thanks >>> >>> Tim >>> _______________________________________________ >>> Repoze-dev mailing list >>> Repoze-dev@lists.repoze.org >>> http://lists.repoze.org/listinfo/repoze-dev >>> >> > _______________________________________________ > Repoze-dev mailing list > Repoze-dev@lists.repoze.org > http://lists.repoze.org/listinfo/repoze-dev > _______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
