Managed to authenticate as undefined

Question

Managed to authenticate as undefined

Closed this issue 14 years ago · 5 comments

Only happened once, the first time I brought up a UOW server, went to the catalog, clicked login, the login popup appeared, the popup disappeared (because I had given google my permission in the past), the login deferred reported success, but my user info came back with all undefined fields and role of "anonymous". I tried uow.getUser() immediately after this happend and got the same info.

So somehow, the triggerLogin method indicated success but was missing the user info or the login actually failed.

Answer 1 · 2010-09-01T10:10:03.000Z

Ah, this must be what Charna at the center did. Look in your logs. I think you can see the response from Google. Somehow the response must have been different than expected.

Answer 2 · 2010-09-01T10:17:22.000Z

I see we are way behind on tornado updates and I see discussion of a similar sounding problem here: http://groups.google.com/group/python-tornado/browse_thread/thread/4e9db1e1cfb0c472/f0aef08a67204235?#f0aef08a67204235, perhaps we just need to update.

Answer 3 · 2010-09-01T11:52:06.000Z

I'm going to add a test to _on_auth in access.py. Currently it tests that user is not empty. I'm going to additionally test for an email address before signaling OK on the login. At least the login will fail if this case happens again.

Answer 4 · 2010-10-09T01:47:42.000Z

I haven't seen this in a while. Can we close?

Answer 5 · 2010-10-09T10:05:11.000Z

yes, this is fixed.