Comments on: Edge Rails, OpenID and the Dreaded Sorry, the OpenID verification failed” error

By: Ernest

Ernest — Sun, 20 Dec 2009 08:59:02 +0000

Hello,
I got the same issue now with Rails (now version 2.3.5). OpenId was working, but now this dont work, I dont know what is going on .
Thanks in advantage for response.

By: Tiago Macedo

Tiago Macedo — Thu, 22 Nov 2007 20:11:53 +0000

It’s been merged.

By: Tiago Macedo

Tiago Macedo — Thu, 22 Nov 2007 01:01:53 +0000

I turned your fix into a patch with a failing test.

Hopefully it will be merged in time for Rails 2.0.

Thanks!!

By: justinball

justinball — Thu, 15 Nov 2007 17:41:26 +0000

I submitted a ticket for this issue. We’ll see if a fix shows up in Rails 2.0.

By: Tyler Hunt

Tyler Hunt — Fri, 02 Nov 2007 02:49:44 +0000

Darrin, thanks for the post. That does indeed seem to fix the issue. Have you submitted this as a patch? I ran the unit tests for ActiveRecord after making the change, and everything passed, though I suppose there should be a test created to prove the validity of the fix.

By: Darrin Smith

Darrin Smith — Wed, 10 Oct 2007 12:34:21 +0000

Poking around with this very issue tonite it would appear that the changeset is broken in the docoding of bytea’s (lines 78 and 88) the regexp should be /\\\d{3}/ not /\\\\\d{3}/ as it is in both cases.

A bit of tinkering has shown me the main use for byteas (images) often have a \ followed by a character that requires encoding so they generally match the original regexp and therefore nothing is noticed.

By: justinball

justinball — Tue, 09 Oct 2007 02:32:06 +0000

I haven’t had any luck yet. To tell you the truth I haven’t had much time to go back and look at it so for now I have locked my rails version at 7328 so that it keeps working. Scary thing is that until this problem is fixed I won’t be able to move to the newest version of rails.
Run this:
rake rails:freeze:edge REVISION=7328
and you will be back up and running for now.

By: Tyler Hunt

Tyler Hunt — Tue, 09 Oct 2007 01:34:06 +0000

Any luck figuring this one out? I’ve been trying to resolve the same issue myself for the past few weeks, but I’m stuck at this point and don’t know where else to turn. It looks like you’re the only one out there who has documented the issue. I’d post a ticket on the Rails Trac, but I still haven’t figured out exactly where the problem is occurring. I believe that’s it’s somewhere in all the changes to the binary encoding/decoding, but I don’t know enough about the innards of PostgreSQL or Rails to be able to say with any certainty where the culprit lies.