Portal Home > Knowledgebase > Articles Database > Registration integration?
Registration integration?
| Posted by Karl, 05-28-2009, 08:06 AM |
| I'm running IP.Board 2.3.6 and a gaming ladder (like GameBattles) however, my visitors are finding it annoying that they have to sign up to each of them seperately. IP.Board and the ladder system both have a different MySQL database, a different registration form, and a different log in form.
What's puzzling me is how I could connect them together, so if you sign up on one, it signs you up on the other without anything going wrong. I'm not amazing with PHP or MySQL so any help is appreciated.
Thanks
~Karl
|
| Posted by rnvr, 05-28-2009, 08:38 AM |
| If you have two different table for the different parts of your site, make a UNIQUEIDENTIFIER for a user, and add that column in both tables. as soon as the user logs in on part of site, maintain cookie or store session info by UNIQUEIDENTIFIER and automatically logs into other part of site....
hope it's not a spam...
|
| Posted by tuxguru, 06-02-2009, 07:00 AM |
| Make a wrapper signup script which adds entries in both the application databases and use it for all signups.
|
| Posted by mwatkins, 06-02-2009, 10:57 AM |
| The bottom line is you'll need to analyse the login requirements of each application and then come up with a common approach - like a single sign on "wrapper" as suggested by tuxguru.
A wrapper or single sign on page might be done by directly replicating some of the sign on code of each. This would entail getting intimate with each app's code. As tuxguru pointed out you could help prevent user management / synch issues by having your code add entries to both apps. But now you have a situation where you may want / need to disable user profile management in each app and centralize it. The list goes on.
Its possible you may be able to keep some separation from the other apps code - i.e. don't touch it - by issuing two "Ajax" requests made to each of the applications from your single sign on page. But you are left with ensuring users have the same ID on both systems. To do a good job you'll likely need to disable user management in the individual applications and redirect such requests to the new app you'll be writing.
In that scenario you create a uber-user management database and set of forms where they can add their information for all the apps on your "site".
Or ... There are no "easy" answers.
Or you could tell your users to live with it.
Last edited by mwatkins; 06-02-2009 at 11:05 AM.
|
| Posted by HivelocityDD, 06-02-2009, 12:04 PM |
| It is always better to use a service like gmail and orkut. Make a centralized login system. Where you keep a cookie to store the login informations. You can make use of curl for authenticating in another case if you are using common login details in both applications.
|
Add to Favourites 
Print this Article
Also Read
