commenting out the return_to in finishOpenID did the trick (it will take the return to as defined in the constant. The URL only provides a path without the servername.
So two minor changes made it work... On Tue, Jul 21, 2009 at 22:07, Hans Donner<hans.don...@pobox.com> wrote: > I've used Massimo's code, installed it in a new app and executed it > (using myopenid). > > I'd had to change > #trust_root = 'http://127.0.0.1:8000/openid/client/startOpenID' > trust_root = 'http://127.0.0.1:8000/openid/client' > return_to = 'http://127.0.0.1:8000/openid/client/finishOpenID' > > to give me a proper reponse > > Otherwise I got: > u'http://127.0.0.1:8000/openid/client/finishOpenID?janrain_nonce=2009-07-21T20%3A03%3A08ZydTT8V&openid1_claimed_id=http%3A%2F%2Fuseyouridhere.myopenid.com%2F' > not under trust_root > u'http://127.0.0.1:8000/openid/client/startOpenID' > > > Does that help you? (the error message you posted is not helping here) > > The next stop is web2py's response: > message > : > something heppened:{'failure_reason': "return_to does not match return > URL. Expected '/openid/client/finishOpenID', got > 'http://127.0.0.1:8000/openid/client/finishOpenID?janrain_nonce=2009-07-21T20%3A04%3A27ZN8rsX1'", > 'error': 'OpenID authentication failed.'} > > > > On Tue, Jul 21, 2009 at 10:46, Bottiger<bottig...@gmail.com> wrote: >> >> I don't need wireshark. Its in plain sight. The problem is I have no >> idea what is wrong with it. >> >> https://open.login.yahooapis.com/openid/op/auth?openid.assoc_handle=crOLLLvQds2YOP5jXvLaBs1gVC1eIpFhqmxcDxETwNFxG68HIItiJzZhrffh4bn00jyuPgNt2clv3bSaQvG9yNJ8EIx._Ja768i256WwR4sUXnKEMimMy3jd4VJcT2dfcw--&openid.claimed_id=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.identity=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0%2Fidentifier_select&openid.mode=checkid_setup&openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.realm=http%3A%2F%2Ftest.domain.com%2Fopenid%2Flogin%2FstartOpenID&openid.return_to=http%3A%2F%2Ftest.domain.com%2Fopenid%2Flogin%2FfinishOpenID%3Fjanrain_nonce%3D2009-07-21T08%253A44%253A37ZYQiIKa >> >> where test.domain.com is an actual subdomain I own that is mod_proxied >> to web2py. >> >> On Jul 21, 1:18 am, Yarko Tymciurak <yark...@gmail.com> wrote: >>> you might try looking at what gets sent back and forth to try to discover >>> what's wrong; wireshark or LiveHTTPHeaders for Firefox might help... >>> >>> On Tue, Jul 21, 2009 at 3:10 AM, Bottiger <bottig...@gmail.com> wrote: >>> >>> > I've been trying to get Massimo's OpenID implementation to work, which >>> > seems to be the only OpenID implementation for Web2Py. >>> >>> > It doesn't seem to work with either Yahoo or Google, each time saying: >>> >>> > "Sorry! Something is not quite right with the request we received from >>> > the website you are trying to use. Please try again in a few minutes." >>> >>> > I've hosted it on a public domain and changed trust_root and return_to >>> > variables to be valid, so I know its not a localhost problem. So far I >>> > can't figure out what's wrong, as it seems to look exactly like the >>> > Django example on the python-openid site. >>> >>> > Does anyone have similar problems or suggestions? I already know about >>> > CAS and I don't want to use it. >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
