I thought that since I had done "something" with this previously, i'd open up some discussion as to tools and techniques for anyone who has the time and might be willing to publish an integration.
this OpenID class [20] makes the job a whole lot easier.. if you don't use it, it's at the very least a valuable reference. The demo script (included) details how to set "required" (we need nickname and email. still needs server side valid.) fields as well as optional fields (timezone, gender, blah). After submitting your
OpenID [21] URL into the form, you'll either get some failure junk (try again) or a bunch of "requested/required" vars in the $_GET .. if there are no errors and all of your required/requested info is available, go to the database to see if there is a user by that nickname (openid_identity
URL) and email (and that no other users possess either/or), if so, log them in, if not create the account then log them in in one swoop.
OpenID [22] is not an authentication system. it's an identity system. if it were to be used as an authentication method, i'd recommend setting up a restrictive (untrusted) group specifically for
OpenID [23] users.. if you set up another table to track their logins, you could move them out of the untrusted group after a designated "trial" period.
that's all i've got.. maybe it's useful.
edited by: InvalidResponse, Mar 10, 2007 - 02:50 PM
--
http://www.invalidresponse.com [24]
[17]
[25]
