Blog Documentation Try Vanilla Cloud
Please upgrade here. These earlier versions are no longer being updated and have security issues.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.

Migration from ProxyConnect

This discussion is related to the Vanilla jsConnect addon.
JasonBarnabeJasonBarnabe Cynical Salamander ✭✭
in Vanilla 2.0 - 2.8

I currently use ProxyConnect 1.9.9 with Vanilla 2.0.18.1. I'm thinking of moving to jsConnect. Will users who previously signed in via ProxyConnect still be "connected" to their accounts if I use jsConnect? Does jsConnect use the same table to maintain the association?

UnderDogTodd

Comments

  • ToddTodd Chief Product Officer Vanilla Staff

    We use the same association, but you'll need to make your jsconnect use the same client ID as you used for proxyconnect. Do this right before launch.

    1. Backup your DB!

    2. Look in GDN_UserAuthenticationProvider and you should see a row with proxyconnect somewhere there.

    3. Make note of the AuthenticationKey.

    4. Delete the row.

    5. When you add the jsconnect connection use that AuthenticationKey for the client ID.

    UnderDog
Sign In or Register to comment.