Using vBulletin Authentication for Other Site Area Login

[tcb1218]

We are developing other applications on the site that will require users to login. We want a single logon for the site including vBulletin. I have looked at the threads on LDAP and it looks like a good solution but would be an over kill for us. It seems that the most straight-forward solution is to use vBulletin's authentication for the other site areas. So if a user hits another area on the site, they would be routed to the vBulletin login then sent back to the page they came from. Is this possible? How does vBulletin keep track of authenticated users so that we can develop the other areas to use the same mechanism to determine that the user authenticated through vBullentin. Another way would be to route the user to a page we develop to authenticate and the code would perform the same functions as the vBulletin authentication. Can you please point to some documentations and/or examples on how this may be accomplished. Input on other ways to accomplish the single logon would also be appreciated. The rest of the site's backend will be developed in Perl ( no flames on using Perl, please :- ) ).

[Wayne Luke]

Usually if you include the vBulletin Engine within your projects, it will load Class_core and make everything available to you. So what you want to do is possible and actually the easier way to do it overall.

We have a community at www.vbulletin.org that can help you with this kind of programming questions. But yes, it is possible.