Bingo - I'll start an issue over in google code submit the patch. Thanks
Anthony!
No problem. Glad it worked. Thanks for submitting the patch.
Anthony
On Sunday, July 10, 2011 1:26:06 PM UTC-4, Brian M wrote:
Bingo - I'll start an issue over in google code submit the patch. Thanks
Anthony!
With 1.96.1, Auth was rewritten to use the new thread local 'current' object
as the environment instead of passing globals() to Auth. However, the
'current' object does not include URL (and other web2py global objects), so
auth.environment.URL doesn't exist.
It looks like openid_auth.py
I have spent the last two days battling with this. I was so close for
so long that I could not leave it alone until I figured it out.
I am happy to say that I have OpenID working both on the basic server
and GAE.
You can see my struggles and the final result here:
At first I struggled with OpenId myself, using the python-openid lib. It did
cost me several nerves and reading many other implementations was necessary
before I understood the inner workings. But now I do - it was worth it, and
I got a simple login working. Then I wanted to combine it with
Thanks for your hint. Upon Janrain I already stumbled because of their
python-openid lib. For my current project I only need Google, and so I would
really like to not enroll with another 3rd party. Besides, Janrain wants to
have the domain registered with them. Wouldn't that mean to register
Well I only used it once, but from memory registering was a piece of
cake and I thought you could enter several domains in the same
account, so I don't think that would be an issue. You get free usage
for up to 2500 users and then you have to pay. But it's not really so
expensive. Maybe worth a
Sorry this doesn't directly answer your question, but...
for this kind of remote authentication people seem to have put most
effort into Janrain. This includes support for:
Aol, Yahoo!, Facebook, Twitter, LinkedIn, Google, MySpace, Windows
Live, PayPal, Hyves, Verisign, MyOpenID, OpenID,
8 matches
Mail list logo
