Best practice for developing site with openId - user table?

Question

I'm quite new to OpenId and I'm having a bit of a problem understanding how to use the OpenId once the authentication is complete.

I'm creating a new site, and I've had no problem in getting the openId authentication working. But I'm not sure how I should store user related data once the user is logged in.

Before openId, I would have my own registration process, a UserTable with a unique UserId (integer), and all other tables involving data related to some user activitiy would just have a UserId column identifying the user.

Should I now use the OpenId id in my tables? Should I create a really simple OpenId->UserId table that every login is mapped to and have data stored as previously? And what happens when a user want to use different OpenId providers?

Answer 1

I'd suggest that you have user id to OpenID mapping, just because it would make sense to have it one-to-many — it is a good practice to allow people have more than one OpenID identity bound to the account.