Livefyre – Registration


This topic explains how to integrate Livefyre with Janrain’s Registration (Capture) solution.


Configure Backplane Settings

Add these JavaScript settings to the HTML page where Registration resides.

Backplane Integration

Registration complies with the Backplane Protocol. You can configure it along with other Backplane-enabled apps to share information through messages sent from a central server. Refer to Backplane Protocol for more information.

Note: When making these settings, you must enter the whole line (like in the following example). If you omit .capture the setting will not work. See Settings for details.

User Migration

On a site with existing users, Janrain will migrate the users into your Registration application. You must provide a data file of the users in a .csv file with all columns properly labeled and mapped to the appropriate Registration schema field.

Users will be migrated into your development environment as a test. Once confirmed and approved, the users will be migrated to the production Registration instance. You can schedule changes to the user data up to production launch (to import or update any users that have been added after the initial user data was imported).

Note: Users must be imported in both your development and production applications of Registration before Livefyre can import comments.

Livefyre Setup and Data Migration


You must provide the following things to Livefyre:

Note: This identity URL cannot be a CNAMED record (that is, a vanity URL) that eventually resolves to the actual CNAME of the Registration instance. This is because the data received by Livefyre references the actual CNAME, as opposed to the “vanity URL” CNAME.

Your Registration app schema must have the appropriate Livefyre email notification fields and have one of the following possible default values set for new users:

Field Name Field Type Description
comments string Possible values are immediately, often, and never.
likes string Possible values are immediately, often, and never.
replies string Possible values are immediately, often, and never.
moderator_comments string Possible values are immediately, often, and never.
moderator_flags string Possible values are immediately, often, and never.
autofollow boolean Possible values are true and false.

You can perform the migration either with, or without, profile migration. We provide instructions for both below.

Without Profile Migration

Livefyre steps:

  1. Create a schema for mapping Registration fields to Livefyre profiles.
  2. Add Registration settings and credentials.
  3. Add Social Login credentials.

With Profile Migration (Additional Prerequisites)

Your user profile data must be imported into your Registration app before Livefyre can start mapping.

Note: Because Janrain’s UUIDs change between Integration (Development) and Production, this mapping is unique to each environment.

Livefyre steps:

  1. Create the schema for mapping Registration fields to Livefyre profiles.
  2. Add the Registration settings and credentials.
  3. Add the Janrain Social Login credentials.
  4. Retrieve user profile data from Janrain.
  5. Create the mapping between your user profile IDs to Registration UUID.
  6. Import your user profile data.

Additional Integration Points

Some additional things need to happen before your integration is complete.

Authentication Delegates

To connect the Livefyre Comment Stream with the Janrain authentication flow, the Stream exposes four (4) hooks (referred to as authentication delegates in the Livefyre integration documentation). You must configure these delegates to perform an action when the following events occur for the Livefyre platform:

Profile Updates

Profile updates are also known as Ping-for-Pull.

When a user updates his or her profile or account, the information is successfully saved in your Registration app, and Livefyre must be made aware of this update. On a profile update, Livefyre should be pinged in order to pull down the latest information from your Registration app.

Backplane Plus Registration


Your website must initialize the Backplane JavaScript on the page (with appropriate channels and settings).

Backplane Version 1.2

Livefyre currently defaults to the Backplane version 1.2 implementation. Unlike when using the standard integration, Backplane requires the client application to change the authentication delegate type to be Backplane-specific, then pass in a reference to the Backplane object that’s available on the page.