User authentification integration
 

I need to integrate the user authentication between vBulletin 3.5.1 and another script's user database.
Specifically, when the vBulletin user account is created, the same user account is created in the other script's database. Only single login is needed. Password changes affect both. Etc..

Am looking for advice on an approach to take to code an integration between vBulletin user authentication and another script's user database.


Am particularly interested in hearing from folks who have done this before, such as:

- Brian / Zachary, the vBAdvanced brains
- Tamarian, who did the vB Drupal hack that included login integration with Drupal
- leitel / Kai Blackman, who wrote the really interesting summary on MediWiki integration https://vborg.vbsupport.ru/showthread.php?t=93024
- Grim77, who did the SigmaChat integration
https://vborg.vbsupport.ru/showthread.php?t=93833
- Pseudomizer, who did the DigiChat integration
https://vborg.vbsupport.ru/showthread.php?t=83102

It seems several people have asked this before, but it has gone unanswered:
https://vborg.vbsupport.ru/showthrea...ad.php?t=69682
https://vborg.vbsupport.ru/showthread.php?t=72134
https://vborg.vbsupport.ru/showthread.php?t=93499

Martin

There is another recent thread about this.. I posted the code I have so far.
https://vborg.vbsupport.ru/showthread.php?t=101721
I have half of it working.

Excellent, monotreme! I'll check it out.

Keep it up!

Martin

I'm also trying to integrate the Vbulletin authentication into my own custom login process. I'm not sure what the best approach on this.

Option 1) Have the custom form post to VB's login.html and then hack that page to header redirect back to my own script to complete the registration. This would mean I'd have to keep all usernames and password synced, which I'd rather not do.

Option 2) Try and copy and modify the VB login process to manually authenticate the user. Trying to do this has proven to be extremely difficult.

Just include global.php in your custom page, and if wanted provide a login box.

I thought I had it whooped and then it went all to heck when people started having multiple forum pages open etc. I'm trying another approach where theres not so much masquerading. basically, instead of curl to vb's login, just set up the form directly on the third party site to be compatible, and go there direct, then the thought is to write a plugin to trigger when vb successfully logis in someone to curl back to the third party site and call a script to do whatever it has to do invisibly. It's cleaner too, in that hopefully we won't have to be patching sessions in vb's database. that's why I deleted that other post, I don't think that's the way to go because there's too much context to duplicate and if vb ever changes their login it would break anyway.