Sync with Livefyre Using Ping for Pull

Use Ping for Pull to keep Livefyre in sync with your user management system.

In general, you Ping Livefyre any time a user of your website/app updates their profile (display name, avatar, etc.), and Livefyre Pulls that user’s updated profile.

Ping for Pull Sequence:

1. Customer sends Ping request to Livefyre (including the User to be updated).
2. Livefyre confirms receipt of Ping with HTTP 200/Success.
3. Livefyre processes Pull request.
4. Livefyre queues Pull request.
5. Livefyre executes Pull request to endpoint to capture updated user info.
6. Customer receives Pull response, and validates.
7. Livefyre updates Remote Profiles with the external profile info included in the Pull endpoint.

Ping Livefyre whenever a user updates their profile information. While Ping for Pull completion time can vary depending on network load, it will update user information in between 1 and 10 minutes. Updated profile changes will display first within Livefyre Studio > Users.

Updated Profile information will appear in your Livefyre Apps after two events:

• A user logs out, then logs back into the App. Display name values in the userAuthToken take precedence over Ping for Pull updates. A user logout/login will refresh the token to update the session.

  To generate new userAuthTokens when profile information is updated, use the SSO authDelegate to log your user out then in again in the background.

• A bootstrap update to the Collection will bring in the updated information (at most every 5-10 minutes).

To implement Ping for Pull for your User Profile system:

1. Build the Pull endpoint.

   NOTE

   The Livefyre library includes a syncUser method for keeping your user profiles up to date. Skip the next two steps if you use the Livefyre library.

2. Register the Pull endpoint in Studio.

3. Build the Ping.

4. [Build the Ping for Pull Response].(#reference_n3x_pzb_mz)

Business.Adobe.com resources