Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an invite-only website. And I would like the users to have the possibility to register with either my own register form, or that they can register with Facebook/Twitter – after they get an invitation from an existing user.
Once they are registered, I would like them to only use my website’s login form to log in. The question is: what is the best way to approach this, is this a good idea to start with?
What I’ve done in the past is create 2 tables (assuming you are using a standard SQL database): one representing accounts and one representing authorization techniques. You can then create a row in the account table for a user and then create a separate row in the authorization table that indicates whether the auth is username/password (in which case the row has the password hash) or facebook (in which case it has the fbuid). You can then look up the account from the auth table when a uer chooses their login method.