I have recently took 1.9.6 and integrated it with a site built in classic ASP that has it's own membership information.
I have to admit, it was quite a bit of customization, but is still doable given the right skills, understanding databases and the YAF architecture.
In a nutshell:
- I had to remove password encryption because the existing membership passwords were in clear text.
- I had to remove all options to update a users profile since we already had that function on the existing classic ASP site (I just added links to reset password, update profile to send users to the existing ASP website).
- I had to remove registration since we want to our membership DB to be the primary DB.
- The meat of the integration was in yaf_login where I created a Linked Servers between two SQL DBs. I did much of the business logic in that sproc to check to see if the users were active, etc. If users did not exist in YAF, but they existed in the main Membership DB, I would insert them. I would also update their information if I see that the profile has changed.
- One snag. How do I know what the users time zone is? Since I allow registrations through YAF, they dont have the ability to set their time zone. So, within the login functionality, I grabbed the GMT offset from the client computer. Granted, it is probably not the best way because I am assuming their computer time is correct, but it works. Of course, YAF time zone is the opposite from javascript gmt offset, so I just multiplied by -1.
Again, there is a lot of customization and more than I had ever thought there would be.