On Sat, Jun 6, 2009 at 2:23 PM, Ricky Zhou <ricky(a)fedoraproject.org> wrote:
This is most likely broken on our side - OpenID in FAS needs a lot
of
work at the moment. Let me know if you'd be interested in working on
this - we can get a test instance setup to test changes on pretty
easily.
Thanks,
Ricky
Hi Ricky,
I'm more than happy to test changes for you. Stack Overflow sent me
some information (see below) does this make any sense to you?
Thanks for your help,
Mat
On Sun, Jun 7, 2009 at 3:21 AM, stackoverflow team
<team(a)stackoverflow.com> wrote:
more info here:
http://code.google.com/p/dotnetopenid/issues/detail?id=186
I have confirmed that the
https://login.launchpad.net/+openid OP endpoint is
not
sending the session_type parameter back in the associate direct response
message.
This OP seems to implement OpenID 2.0 (it sends the 'ns' parameter back),
yet OpenID
2.0 mandates that session_type is NOT an optional parameter. In OpenID 1.x,
it WAS
an optional parameter. This is a common bug for OPs and I will talk to
launchpad.net
about getting this bug fixed on their end.
References:
1.1 spec:
http://openid.net/specs/openid-authentication-1_1.html#anchor14
2.0 spec:
http://openid.net/specs/openid-authentication-2_0.html#anchor20
---
http://stackoverflow.com
--
Mat Booth
www.matbooth.co.uk