JavaScript SDK registration overview

ūüďė

The content on this page deals with a legacy feature of the ‚ÄčAkamai‚Äč Identity Cloud (in this case, the JavaScript SDK). If you are currently an Identity Cloud customer and are using the JavaScript SDK, that SDK is still supported. However, if you‚Äôre new to the Identity Cloud the JavaScript SDK is no longer available. Instead, you should use Hosted Login for your login and registration needs.


Registration offers a richly-featured, customizable user profile data storage solution to help you leverage the rich demographic, interests, and friends data shared by your users from their social networks as well as user preferences and other data collected through custom profile fields. It includes a comprehensive site registration system, complete with registration and profile management screens, as well as back-end tools and workflow. It also includes data import capabilities allowing websites to maintain a unified user system for both new and existing users.

Registration manages user data remotely (in the cloud) in a customizable, hosted database where it can be accessed, modified, or exported as needed. This centralized storage for both first-party data and third-party data shared via social sign-in provides a unified view of your users and allows access by other systems such as email marketing, content personalization, and ad targeting platforms. Registration lets you augment your user profile data with data append services to help you gain insights to increase user conversion, online engagement, and monetization on your site.

‚ÄčAkamai‚Äč's Identity Cloud provides two different kinds of registration and authentication services:

  • Social. ‚ÄčAkamai‚Äč manages integrations with over 30 Identity Providers worldwide. ‚ÄčAkamai‚Äč's Social Login¬†dashboard allows you to easily configure new providers and add them to your website. ‚ÄčAkamai‚Äč also normalizes the schema of the profile data returned by each provider.

  • Traditional. ‚ÄčAkamai‚Äč acts as the Identity Provider and authenticates users with conventional username and password credentials. Existing accounts can be migrated into the Identity Cloud¬†without requiring users to reset their passwords if the hashing algorithm used in your legacy system is supported by ‚ÄčAkamai‚Äč.


Registration Workflow

The diagram below illustrates the registration process for new users.

  1. A user clicks the register/login link on a website or mobile app.

  2. An ‚ÄčAkamai‚Äč registration/login screen is displayed, allowing users to authenticate either traditionally or socially.

  3. The user authenticates:

    • 3A: If the user authenticates using a traditional account, the sign-in credentials entered are verified by ‚ÄčAkamai‚Äč.

    • 3B: If the user authenticates socially, ‚ÄčAkamai‚Äč acts as a proxy service and redirects a user to the selected Identity Provider‚Äôs (IDP‚Äôs) authentication screen.

    • 3C: (not shown) The IDP also presents the user with a permission screen asking if the user‚Äôs social profile may be shared. If the user agrees, the IDP will complete the authentication process and return the social profile data to ‚ÄčAkamai‚Äč.

  4. ‚ÄčAkamai‚Äč receives the successful authentication response and any social profile data the user chooses to share. The registration form is pre-populated with any matching profile data. The user has the ability to modify this information and must complete any missing required fields in the registration form. Note that if the user authenticates socially, the user is not required to create a password since the user will log in using an IDP.

  5. When the user clicks¬†Create Account, a record is created in ‚ÄčAkamai‚Äč's user database. Top-level profile attributes are populated with the data entered in the registration form. This can include the data returned by the IDP. The rest of the social profile data returned by the IDP is stored as a sub-profile in the user‚Äôs account.

  6. ‚ÄčAkamai‚Äč generates a short-lived access token scoped with access to only the newly registered user‚Äôs account. This token is returned to the user‚Äôs web browser and stored in¬†localStorage. Subsequent calls to ‚ÄčAkamai‚Äč's database can utilize this access token to manage user data. ‚ÄčAkamai‚Äč completes the registration process by firing a JavaScript event (onCaptureRegistrationSuccess). The site can then create a session for the user by passing the access token to the web server.

  7. A web-based dashboard offers analytical information across a number of demographic and psychographic categories based on the data stored within a customer’s user database.