On Mon, Jan 4, 2010 at 11:57 AM, James Gardner ja...@pythonweb.org wrote:
One tip though, I now believe using exceptions to trigger the 401 and
403 responses and then intercepting them in WSGI middleware is not a
good design pattern. New code I'm working on generates a normal
response in the
On Tue, Jan 5, 2010 at 10:38 AM, Matt Feifarek matt.feifa...@gmail.com wrote:
On Mon, Jan 4, 2010 at 11:57 AM, James Gardner ja...@pythonweb.org wrote:
One tip though, I now believe using exceptions to trigger the 401 and
403 responses and then intercepting them in WSGI middleware is not a
i don't like AuthKit ( no offense James ! - it's just never served my
needs ) and have had to integrate with systems like you describe.
so the tips i can give are this:
- create your validation and cookie-set/expire functions in something
like app/lib/helpers/auth.py
- put the logic you need in
Hi Jamie,
It sounds like you already have a farily sophisticated setup so I'd
recommend rolling your own but using the AuthKit code as an example
for anything you wish to build yourself.
One tip though, I now believe using exceptions to trigger the 401 and
403 responses and then intercepting
James,
Thanks for the response! I'll do as you recommend.
On Jan 4, 12:57 pm, James Gardner ja...@pythonweb.org wrote:
Hi Jamie,
It sounds like you already have a farily sophisticated setup so I'd
recommend rolling your own but using the AuthKit code as an example
for anything you wish to
I'm working on porting an old PHP project of mine over to Pylons. For
authentication this project mainly uses a lot of Postgres stored
procedures. As well as checking valid login attempts, the database
generates and tracks authentication tokens that are stored client-side
in cookies. Each token
