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
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
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
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
Hi Chris
Control was definately one of the concerns. But I am only relying on
a potential pool of
authentication providers (google, facebook, myspace ) for basic user auth.
It is also possible that I may need to run on appengine, so I may take
the approach of building
repoze.who plugins
My experience so far with helping people who want lots and lots of control
about how a login UI works with r.who has not been stellar; this is the only
reason I mention being able to cutnpaste code into a BFG authentication policy.
When you use a custom authentication policy, you can still
HI Chris
Good points raised and could well be an significant requirement. I
have not yet used repoze.who and have limited experience with wsgi
middleware (Beaker with appengine based memcached session store is it)
so I have wondered how you can hook up any ui to the middleware.
T
On Mon, Jan
