OpenID?
Hi there,
Is there a problem with the OpenID module? I get this error when I try to use a Blogger URL as an OpenID (on support.bryght.com as well as my Bryght site:
error:Invalid AuthRequest: 768: Invalid value for openid.ns field: http://openid.net/signon/1.1
While I am able to successfully add a yahoo.com OpenID to my account at support.bryght.com, I get the following error message on my Bryght site:
Request URI is too long
(And it is a really long URL)
Any idea what I could be doing wrong?
Thanks,
Marcia
Is there a problem with the OpenID module? I get this error when I try to use a Blogger URL as an OpenID (on support.bryght.com as well as my Bryght site:
error:Invalid AuthRequest: 768: Invalid value for openid.ns field: http://openid.net/signon/1.1
While I am able to successfully add a yahoo.com OpenID to my account at support.bryght.com, I get the following error message on my Bryght site:
Request URI is too long
(And it is a really long URL)
Any idea what I could be doing wrong?
Thanks,
Marcia
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I applied a patch to the support.bryght.com install of the OpenID module, and that seems to fix things for Blogger URLs. Going to let it percolate (i.e. test it a little more elsewhere) before applying it to the hosted service.
The "Request URI is too long" appears to be server-related, not related to the OpenID module. The URL is long, but not ostentatiously so. I'll get our systems administrators to take a look. -
Inappropriate?Thanks--I'll look forward to that blogger fix patch to be applied to the hosted service!
Thanks for looking at the other error too!
I’m thankful
-
Inappropriate?marciam, as of early this morning, we've released the OpenID patch to the hosted service. That doesn't necessarily take care of the second issue, i.e. the one that says "Request URI is too long". That one we still have on our issues list.
Loading Profile...



EMPLOYEE