I thought I had it whooped and then it went all to heck when people started having multiple forum pages open etc. I'm trying another approach where theres not so much masquerading. basically, instead of curl to vb's login, just set up the form directly on the third party site to be compatible, and go there direct, then the thought is to write a plugin to trigger when vb successfully logis in someone to curl back to the third party site and call a script to do whatever it has to do invisibly. It's cleaner too, in that hopefully we won't have to be patching sessions in vb's database. that's why I deleted that other post, I don't think that's the way to go because there's too much context to duplicate and if vb ever changes their login it would break anyway.
|