Technical Whitepaper

Pluralsight to SuccessFactors Integration



This document describes and provides examples of Pluralsight's integration capabilities as they relate to SuccessFactors. Each implementation is unique and can be customized. Each solution is thoroughly tested before being used in production.

Why integrate with SuccessFactors?

A full SuccessFactors to Pluralsight integration provides a seamless, secure user experience that increases adoption and utilization. We accomplish this via Single Sign On, automated deliveries of our course metadata and the corresponding completion data. Pluralsight has the capability of delivering the data files to; individual emails, FTP/SFTP servers, or API endpoints.

What does an integration look like from start to finish at a high-level?

Every integration is initiated by either the Account Executive and/or Customer Success Manager via a request to the Professional Services team. Working with the Pluralsight Account Executive and/or Customer Success Manager, the Professional Services Integrations Consultant coordinates a kick-off call with the appropriate customer contact/s and SuccessFactors’ consultant/s in order to understand the customer’s SuccessFactors instance, scope the integration, and assign ownership of responsibilities. Following which, the 3 main components of an integration are executed in the following order:

First, we configure Single Sign On, which allows users to pass seamlessly from SuccessFactors into Pluralsight without having to create and manage another set of credentials. SSO increases security, reduces barriers to usage, simplifies license provisioning and eliminates admin time and costs. Setup begins with the customer configuring and sending the Integrations Consultant their SSO metadata from their federated server.

Second, once SSO is in production, Pluralsight provides recurring course uploads (daily, weekly or monthly) via automated delivery capabilities as a flat file (.csv or .txt) placed on the customer’s FTP/SFTP server. SuccessFactors ingests the file and displays the courses as discoverable learning objects that link the user directly to the given Pluralsight course via SSO enabled URLs. After passing through directly to a course, the users now have access to the full Pluralsight suite of features (Paths, Notes, Adaptive Skills Assessments, Channels, etc.).

Third, we close the loop by configuring, producing, and delivering an automated recurring data export of course completion data via the same capabilities mentioned in step 2. We place a flat file on the customer's FTP/SFTP server (daily, weekly or monthly) from which SuccessFactors ingests the data for use in the LMS.

Each component of the integration is covered in depth below.

SuccessFactors Integration Components

success factors integration

1. SSO (Single Sign On)

Single Sign On (SSO) allows for users to pass between two systems without having to manually type in a username and password while maintaining trust between the two systems. It involves passing information about the user to Pluralsight from which Pluralsight creates an account and/or authorizes access. It has numerous benefits, a few of which are outlined below.

Seamless Experience - When a user clicks an SSO enabled link, they are instantly taken to the content they wish to view with no additional identification, authentication and authorization needed. This helps increase adoption by placing Pluralsight side by side with existing internal applications.

Auto Provisioning - Users are provisioned a license automatically upon clicking one of the SSO enabled learning objects in SuccessFactors, bypassing the manual license assignment process.

Issuance Criteria (Optional) - This allows us to accept or reject an individual requesting Pluralsight access based on attributes (i.e. role, team, department, etc.). It’s a simple way to set rules around auto provisioning. Any issuance criteria needs to be passed over as an attribute in the assertion.

Team Assignments - This allows for a user to be automatically placed into a Team within Pluralsight upon license creation. This further automates the setup and organization of your Pluralsight experience. Any team assignments need to be passed over as an attribute in the assertion.

Pluralsight supports SAML 2.0. In order to set up SSO, the Pluralsight Integrations Consultant and customer will need to exchange federated server SSO metadata. This is typically a .xml file with the information needed for federated servers to communicate. Pluralsight’s metadata also exists in the app catalogs of Okta, Azure, PingOne, and One Login.

After the metadata is configured, exchanged and uploaded to the respective federated servers, the Integrations Consultant generates a vanity URL (e.g.<companyname>) and sends it to the customer to test the configuration. Once the customer confirms the connection is working, we are ready to move to step 2.

NOTE: Oftentimes customers will choose to do all the initial SSO setup and testing in a stage environment prior to moving to production. If so, the production metadata must be configured and provided (after testing is complete in stage) to the Integrations Consultant who uploads the new metadata to Pluralsight’s federated server. The customer then retests the connection in production using the same vanity URL previously provided.

2. Course Uploads

In the initial course upload, the Integrations Consultant provides Pluralsight’s course metadata for all 6,000+ courses using the SuccessFactors Item Connector templates. This includes modified SSO enabled course launch URLs for each course. We've pre-configured our templates to align the course metadata with 3 of the SuccessFactors connector templates. They were configured using the Mapping Tables found in section 11 of the Connector Workbooks Customer (1702) document provided by SuccessFactors. They are as follows: Item (section 11.1), Content Object (section 11.2) and Content Object to Item Data (section 11.2). The Integrations Consultant will speak with the SuccessFactors consultant to collect the connector templates required to integrate with the customer’s particular instance of the LMS. NOTE: The Integrations Consultant can replicate the requisite templates if they vary from the templates below.


Course Library Deltas: After the initial placement to and upload from the FTP/SFTP server of our course metadata, Pluralsight provides automated continued deliveries of our course library deltas, to add new and update existing courses, on a daily, weekly or monthly cadence via placement of a flat file (.csv or .txt) on the customer’s FTP/SFTP server for ingestion by SuccessFactors (see “Connecting to the FTP/SFTP Server” below).

3. Completion Data Delivery - Learning History Connector

Pluralsight provides the course completion data on the SuccessFactors Learning History Connector template. We've pre-configured the template to align our course completion data with the Learning History Item Data Mapping Table found in section 10.1 of the Connector Workbooks Customer (1702) document (Example below). We provide automated ongoing deliveries to record new item based learning events on a daily basis via placement of a flat file on the customer's’ FTP/SFTP server for ingestion by SuccessFactors (see “Connecting to the FTP/SFTP Serve r” below).


Connecting to the FTP/SFTP Server:
FTP or SFTP Placement Requirements

  • Desired Cadence
    • Daily, Weekly, Monthly
  • URL for placement (must include the relevant directory)
  • Username
  • Password

After the information above is collected, the Integrations Consultant places a test file to the server. The Consultant then notifies the customer and/or SuccessFactors contact and asks them to confirm the test file has been placed on the server in the correct directory. Upon confirmation, the Integrations Consultant then places the first round of data files (Item Connector/s and Learning History Connector) on the server. SuccessFactors then attempts to pull the files and ingest it into the LMS. When ingestion of the data files is confirmed successful, the Integrations Consultant sets the files for automated delivery of deltas at the specified cadence (Daily, Weekly, or Monthly).

API Placement Requirements (Option available if requested) :

  • Endpoint URL and Authentication key
  • Username & Password

Now what?

Contact your sales representative and inform them that you’d like to engage Professional Services ([email protected]) to complete a SuccessFactors to Pluralsight integration.