Re: Using LiveUser with vBulletin and other 3rd party products

Lukas Kahwe Smith <[email protected]> Fri, 30 Sep 2005 10:53:49 +0200
Newsgroups gmane.comp.php.pear.liveuser
Message-ID <[email protected]>
David Arthur wrote:

> My plan is to use LiveUser as a means of logging in to various systems 
> at once, for example vBulletin and a clients user database.
> I'll first say that I have migrated all users from the clients user 
> database across into the vbulletin database so that the logins work 
> through vbulletin and the rest of the site independantly. I've also 
> managed to authenticate in LiveUser, this happens if the users 
> credentials match the one of storage container, they are logged in. When 
> i say logged in, LiveUser logs in but doesnt create the sessions 
> necessary for vbulletin to treat the user as logged in, I was wondering 
> if anyone has suggestions on dealing with this.
> LiveUser doesnt seem to pull out the fields off any additional 
> containers when logging in. It must just check the first and if they 
> authenticate, not bother with the rest. Is there a way to make it do 
> this, obviously i need the rest of the information before i can start 
> creating the session vBulletin expects, the solution may just be to get 
> it all independantly.

LiveUser currently does not feature a single sign on container. You 
would have to write your own callback for this 
(http://pear.limbourg.com/34.html). You would use the 'onLogin' event to 
log the user into all backends and the 'onUnfreeze' event to keep all 
the session alive.

> Next up is the user admin, its hard to tell if LiveUser can do this or 
> not, but if a user for example changes their email address we want that 
> to go across all containers. I'm still looking into the admin of 
> liveuser but if anyone has tips on how to achieve this it'd be great.

We have not implemented observers in the admin. Even still this would 
probably not be all that useful for your case. You probably need your 
own custom method that wraps around LiveUser_Admin to cycle through each 
of the containers and make the necessary calls.

regards,
Lukas