I upgraded JanRain’s OpenID Library from 1.2.3 to the release issued on 2007-11-16, Version 2.0.0-rc5.
Various things have changed, but I fixed most of them.
One remaining issue is that with
$openid = $response->identity_url;
the entered xri used to be returned (for example, =nat), but this has changed so that the canonical id is returned. Well, that means it now conforms to the OpenID specification, but… As a result, it is recognized as a new user, so I wonder if the RP side needs to retain the entered ID or do something similar… Well, I will ask someone like =masaki about this…
On the other hand, one good point: it is finally compatible with Sxipper.
I need to change the specifications of the module for Xoops a little… Maybe I will organize this area, rewrite it properly, clean up the code somewhat, and then release it… I think the current version is easy to read, but it is messy…
Related posts
What Does OpenID Provide?
Now, assuming that OpenID will be incorporated into Xoops in the near future, what does OpenID provide to the “Relying Party (RP)” (in this case, Xoops…
Two-Factor Authentication Using a Bookmark: BeamAuth
One weakness of OpenID is the problem of phishing. With OpenID, users are redirected to an authentication server for authentication. The problem is that, instead of…
OpenID Is Not a Specification for Authentication
As of 2010/4/29, the Japanese edition of Wikipedia describes OpenID as follows: “OpenID is a standard for an authentication system that can be used regardless of…