Janrain Migration Guide

If you're transitioning from Janrain to LoginRadius, this guide outlines how to migrate your users efficiently. You can choose between Bulk Migration to move all users at once, or Just-in-Time (JIT) Migration to migrate users gradually as they log in—depending on your technical requirements and business timelines.

Migration Types

This section outlines the two supported migration methods and helps you decide which strategy suits your use case.

Migration Type	Managed By	Timing
Bulk Migration	LoginRadius	One-time migration before go-live
Just-in-Time (JIT)	Customer	Gradual (1–6 months), based on business needs

Bulk Migration (One-Time Import)

Bulk migration is a one-time import process handled by the LoginRadius team. You can use the Janrain Entity and Entity Type API to extract or export data manually in CSV/JSON format. LoginRadius processes this data, maps fields, and imports users into your new environment.

Data Sync via Janrain API

LoginRadius utilizes the Janrain Entity and Entity Type API for database migration to retrieve user data from your Janrain Identity Cloud application. You don’t need to perform the export yourself—our migration service handles it securely and efficiently.

To ensure a smooth migration, you'll need to provide your Janrain API credentials, and we’ll manage rate limits and schedule the data export process.

It is important to review the data mapping between Janrain user fields and the corresponding fields in the LoginRadius schema before migration. The LoginRadius Data Point document can help you understand how user attributes will be transformed and stored in LoginRadius. For more details on data mapping, please click here.

Required API Credentials

LoginRadius requires the following credentials to access Janrain’s user data in bulk via the API.

Field	Description
key	This is the API key associated with your Janrain Cloud Application
application_id	Unique identifier of your Identity Cloud application.
client_id	Client ID assigned to the application/client.
client_secret	Client Secret assigned to the application/client owner
Authorization	This parameter needs to be included in the API call. Authorization = “Basic bas64encode(client_id:client_secret)”

Customized Export Migration(CSV/JSON)

Janrain allows user data exports for teams that prefer a manual export approach or cannot access the Entity and Entity Type API. You must securely share the exported file by using the secure methods (e.g., SFTP) and confirm data mappings before importing.

Sample Data Mapping

This table shows how Janrain user fields are translated into LoginRadius format. These mappings are finalized during setup.

Janrain Field	LoginRadius Field
uuid	Uid
emailVerified	EmailVerified
email	Email.Primary
givenName	FirstName
created	CreatedDate
lastLogin	LastLoginDate
familyName	LastName
birthday	BirthDate
updated	ModifiedDate
organizations	Company
profile.currentLocation	Addresses
honorificSuffix	Suffix
honorificPrefix	Prefix

Password Hash Support

To preserve user authentication, LoginRadius supports the most common password hashing schemes used by Janrain. During setup, you must provide technical details like the hash algorithm, salt (if used), and iteration count.

Supported hash types include:

• bcrypt

Just-in-Time (JIT) Migration

When migrating from Janrain, Just-in-Time (JIT) Migration provides a flexible, user-friendly approach to onboarding users into LoginRadius. Instead of transferring your entire user base at once, JIT migration provisions users only when they actively log in. This helps ensure that only verified and engaged users are migrated, streamlining your data and reducing the risk of importing inactive or outdated records.

Uses of JIT Migration

• No bulk imports required

• Seamless user experience during transition

• Cleaner data hygiene—only migrate active users.

• Highly customizable to fit your existing infrastructure and business logic

Methods of JIT

LoginRadius supports two methods of JIT migration:

• API-Based JIT – Ideal for teams that want complete control over the login and provisioning process through backend logic.

• Orchestration-Based JIT – Perfect for teams that prefer a low-code approach using the LoginRadius Identity Orchestration Engine.

Both methods authenticate the user against your existing identity provider (Janrain). If authentication succeeds and the user doesn't already exist in LoginRadius, the profile is created automatically. All future logins are handled through LoginRadius.

Orchestration-Based JIT Migration

If you want to skip writing backend logic, then you can use the LoginRadius Identity Orchestration Engine to handle JIT migration visually. To get started:

1. Download the sample workflow json file.

2. Navigate to Orchestration > Workflows in your LoginRadius dashboard.

3. Click New Workflow and import the JSON.

4. Once loaded, use the External Identity Lookup node in LoginRadius to configure a call to your Janrain login or user info endpoint. This typically involves setting the HTTP method (e.g., `POST`), endpoint URL, request headers, and a request body that includes user credentials or identifiers.

To learn more about this feature, check out the Identity Orchestration Overview.

API-Based JIT Migration

Here’s how to implement JIT migration using backend APIs:

User Login Attempt

The user initiates a login using email, username, or phone. Your backend intercepts the request and checks if the user exists in LoginRadius:

• Check Email Availability
• Check UserName Availability
• Phone Number Availability

If the user exists, proceed to authenticate using:

• Login by Email
• Login by Username
• Login By Phone

User Not Found in LoginRadius

If the user does not exist in LoginRadius:

• Authenticate the user using Janrain Authentication traditional login API
  https://techdocs.akamai.com/identity-cloud/docs/complete-traditional-login.

• The above API will return the access token of Janrain. Now, you can call the following API to fetch the user profile https://techdocs.akamai.com/identity-cloud/docs/view-userinfo-information.

• Upon successful validation, use the Account Create API to create the user in LoginRadius:

  • Include identity details (email/username/phone)

  • Provide the password and any additional profile fields.

Note: The Account Create API requires your API Secret and should only be called securely from your backend.

Future Logins

Once the user is created in LoginRadius, future login attempts are fully handled by LoginRadius, with no further calls to Janrain.

LoginRadius APIs to Use

Depending on where your migration logic runs, use one of the following:

Backend (Secure) API

• Account Create API – Requires API Secret (backend only)

Frontend-Safe API (Optional if you avoid secrets)

• Auth User Registration by Email – For non-sensitive use cases

Related Documents

• Data Migration Security and Sanitization
• Customer Identity API
• Identity Orchestration