last i looked - no, the password created from the vB integration into G2 will not work in standalone.
at least - not the way you want it to...
supose my password is: 123
so i go to vB and log on w/ my password of 123.
vB takes that '123' and adds it's SALT to it. i'm not exactly sure where/how, but that's what it does. so you enter '123' and vB sees 'SALT(123)'.
thus, the G2 integration script sends 'SALT(123)' to G2 as my password.
so - now i log out of vB and visit the standalone G2.
i attempt to log on w/ my password of '123' and get denied. because my password is not '123' but 'SALT(123)'.
so you'd have to do some code modification (sorry, i havn't looked into this myself nor plan to) to make the G2 authentication go through the same SALT as vB does or soemthing to that effect...
however - on the G2 forums, the user 'valiant' who works w/ the integration side of G2 has added SALT integration to the todo list. but on a low priority as aparently not a lot of CMS and/or forums use it in this manner.
i do have to add the 1 disclaimer that this information was based on about G2 RC2 and i havn't looked to see if it's been worked into G2 final. so u may want to research that!
HTH
|