Rails + openid-login generator = Parameter action does not match return_to URL

Tick theaterfire at yahoo.com
Tue Jan 29 06:20:49 PST 2008


--- Kevin Turner <kevin at janrain.com> wrote:

> The hash you're sending to complete() includes "controller" and "action"
> items.  I'm guessing those weren't really parameters that were part of
> the request like openid.mode is.  Pass only the arguments that were sent
> by the browser in the GET or POST and it should behave better.

This was exactly the problem.
 
> The example code contains this line:
> 
> parameters = params.reject{|k,v|request.path_parameters[k]}

And this fixed it.

Thank you so much!  As a casual developer, this has been tying me up for a
couple of weeks.  I'd been working from other external examples that were
much less clear and I hadn't yet dug into the rails app that ships with
the ruby-openid gem to find out how it works.

Is the rails openid-login generator that ships with 2.0.3 still
maintained?   It generates code that feeds the raw params hash directly to
consumer.complete().  It also assumes that the return value from
consumer.begin() will have a #status property, which looks to be a
holdover from ruby-openid 1.x.x when begin() returned an OpenIDStatus
object instead of a CheckIDRequest.  Perhaps it hasn't been updated for
ruby-openid 2.x.x? 
 
Thanks again!


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 




More information about the Dev mailing list