2154000 - Cross-Domain Communication Restriction - Learning Management System

Content can communicate with Plateau using one of two technologies:

• a direct HTTP Post
• a client-side API

AICC content uses direct HTTP posts to send information to Plateau

SCORM content uses a client-side API

The Plateau Tracking Functions can use either direct HTTP posts or a client-side API. When content is using a client-side API for communication, that content must be hosted under the same DNS as the API it is attempting to use. If the content and the API are hosted under separate DNS names, the browser will prevent them from communicating.

It is important to note that this is not a Plateau specific issue. It is a restriction that is inherent in the SCORM communication standard.

In the diagram above, the content and the API's are hosted under the same DNS.
As a result, the content can access both the SCORM and Plateau Tracking API's for communication.

In the diagram above, the content and the API's are hosted under separate DNS names, preventing them from
communicating with one another. Under this scenario, only direct HTTP posts may be used for communication.

If it is necessary to host your content under a separate DNS, several solutions exist to work around the cross-domain restriction. ADL, the writers of the SCORM spec, have compiled a collection of potential solutions for the cross-domain issue. This paper is available on the ADL web site (http://www.adlnet.gov):

Solutions discussed in the ADL paper fall under three categories:

1. Combination LMS and content solution
2. Network architecture solution
3. LMS-based solution

SuccessFactors Learning Management System (LMS) - All Supported Versions

SF SuccessFactors LMS Learning Cross domain cross-domain communication restriction , KBA , LOD-SF-LMS , Learning Management System , LOD-SF-LMS-CNT , Content , How To