Time to think - so much talk about integration.. bridges.. very little code.

[psalzmann]

A thought came to mind when searching through hundreds of posts regarding integrating any "other" application with vbulletin (any version). It seems everyone is complicating this entire process. But I could be wrong

Now, correct me if I'm wrong here but wouldn't this solve everyone's problems?

Requirements:

• vb forum and "other app" reside on same server
• function to update the "other apps" user info (user/email/pass)
• function to create the "other apps" user data (user/email/pass)
• function to delete the "other apps" user data

Goal:
Main vBulletin forum is the source of members. In order to provide a multi-login feature the "other app" must know about the vb user information (username/password/email).

Additional Goals:
We do not have to search and replace functions in vbulletin files or edit scripts to the point where it becomes time consuming. When a vb user updates their info or if an admin updates or adds new users, I'm thinking we only need to modify 2 sections in the VB php scripts which may also be easy enough to actually create hook hacks in these places (I will do this ASAP if someone can pin-point the hooks just after the user uses the login menu and the hook placement before and after the "remember me" functions auto-logs the user into the vb (creates session; ie: $bbuserinfo['xx'] arrays))

The trick:
A vb admin creates a new user in the admincp. That user is not automagically added to the "other app" -- yet, that process actually happens when the new user the admin creates actually logs-in to the vb forum -- using the actual vb login menu. This also means, if your forum has 10,000 members, and 8,391 members actually "login to your forum" when this hack is installed, then 8,391 vb forum users will also be members in the "other app". No need to clutter your "apps" database with users that might never relogin to your forum anyways. Right?

Additional thoughts:
The remember me function in vb below will additionally trigger the checkup script function to see if the user is active in your "other app" since he may have registered, verified his link code via email and then uses the "login menu" or for boards that disable link code email validation, the remember me would create that new user in your app.

Also, a delete function can be triggered when the admin "deletes" the user from the AdminCP. (Can someone please give me the hook name for this exact code flow - much appreciated)

I think that covers it all! Doesn't it? Please advise your thoughts.


So, with that in mind:

1. Login Menu
2. Remember Me Code Logic

During these two code blocks, wouldn't it be possible to write a simple function that will:

1. Check if the vb user logging in (from a vb login menu) exists in the "other app",

If so [do a quick check to see if the info is the same ( user / pass / email ) ] and skip .. [or update as necessary]
if not, create that user so they can login to the "other app" using their existing vb login details (at some point).

The point above: Actually creates the new user in your "other app" if they do not already exist.

2. I assume that the remember me function in vb will run some sql code to ensure the member is logged in from page to page (can someone please confirm this?) (based on the created cookies of their web browser). If this is the case, the additional function will also check to see if the vb user exists in the "other app" and if so, do a check up to see if the username, email or password is different, if so, update the "other apps user table" with the currently logged in vbulletin user [again, based on the username, email and password [and/or password salt]).

Suggestions? concerns? thoughts? I'd like your input. I will create the hack for everyone here, I just need some help in finding those hook placements. Please save me some time, and I'll return the favor

Regards to everyone at VB.ORG and have a safe and merry holiday!