When should I use setUID vs. notifyLogin?
Most sites choose to use the Gigya service as an additional authentication mechanism on top of their existing authentication mechanism. You may find an example of an existing registration form, alongside with Gigya’s Plugin on the Login page of Gigya’s website (if you are logged in, log out to view the page). When a user opts to login or register to your site, you can offer the user to authenticate using either Gigya Plugin or your existing Login/Register form. Each of these two options leads to a separate logic flow. notifyLogin: When a user authenticates using your existing Login/Registration form, it is important to notify Gigya of the user’s new state, so as to provide consistent user experience. To implement that, call the socialize.notifyLogin API method at the end of you existing authentication flow. setUID: This method replaces the Gigya UID in the user account on Gigya’s DB, with a site user ID that you provide. This operation practically links the current user’s Gigya account
