Embedding vBulletin into an ASP-based site.

[poi@nwdnb]

Hi there.

I have been brought onto the development team for a website that we are building in ASP VBScript. My preference is of course PHP but this is not to everyone's taste so ASP is the way things are going. We have been running VBulletin (on a seperate linux server) for some time now, and are very pleased with it.

The main ASP site will have support for members to log in and modify certain sections we allow them to (a la vBulletin user groups), and I am looking for a solution, so that users can use the same login name / password for the main site, and the forum, and when logged into one or the other, they are logged into both.

I suspect we can make the ASP login scripts act as a "wrapper" for the vbulletin login sequence, and then it would just be a case of utilising the cookies generated by the forum in the ASP scripts.

Does anyone have any experience with this, or any pointers as to how we might move forwards?

I appreciate this isnt really a vbulletin question as such, but any input would be greatly appreciated.

[Scott MacVicar]

You can use ODBC in ASP to connect to the mysql server for checking username / pass. So its not really that hard, the other people on the team should have no bother with that.

[poi@nwdnb]

Thanks, we have made some progress with this since i posted.

It appeares you cant connect to MySQL without installing MyODBC (an ODBC driver provided by the people who make MySQL), and as we dont have administrative rights on the server this isnt an option.

I have instead just put a login form on the ASP site that submits to member.php to log in users, and then the ASP site just checks for the presence of the bbuserid cookie. This works for us luckily, because both sites are on the same domain (different subdomains tho).

It means obviosuly i cant access the MySQL vbulletin database, but this is something that can be worked around for us.

We were going to do as you said PPN, and just use the one MySQL database for everything, but we hit up against this necessity of MyODBC problem.

Thanks for your input tho