Quote:
Originally Posted by thethinkingman
Thanks for the help as always everybody.
That being said, I have been informed that the project was not correctly described to me the first time around, so I need to restate the issue.
While we have enough PHP programmers in house to accomplish a bridge (and thank you guys to letting us know that is possible  ), we do not know the vBulletin passwords nor user names that we would need to know in order to develop the seamless link (or SSO) from the already established user names and passwords from our website to vBulletin. That being said, does anyone know of a seamless link/SSO solution to such a problem?
This is a tall task, so I am not sure a solution exists, but i just thought I'd continue to throw that out there and see if anyone had experience in a similar situation.
|
Most of these bridges are better done in-house. Many of the released hacks have problems and bugs and can use with a bit of work. There are some road blocks that needs to be cleared with file paths and stuff when integrating the vBulletin user system.
Once these are blocked you could go several routes with your user bridge:
- Start out by importing all users into your vBulletin, the modifying your site's code to revolve around vBulletin's user system.
- Building a modification to vBulletin to fetch usernames from your site, this may cause problems in the long run.
- Build a script that syncs the databases and when logging in / out, modify the setting of cookies to add two. One for vBulletin's login and an identical one for your site login.
Personally, I recommend using the first option, especially if it is a custom CMS. The only problem with importing your users into vBulletin would be the md5 hashes. You can require that all users reset passwords or if you have too little hashes (because I believe vBulletin uses md5() several times) you could, upon writing the import script bring your passwords with more md5 hashes before sending them into the database.
You can go several routes with this.