CORS error in SCORM XBlock

Hi all,

I’m experimenting a CORS error when using a SCORM XBlock in my Tutor K8s - maple. The backend is S3, and the SCORM was unpacked and loaded properly in the bucket by the XBlock in Studio.
In the local installation it is working.

The log shows:

0:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - <h1>SCORM Driver starting up</h1>
1:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - ----------------------------------------
2:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - ----------------------------------------
3:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In Start - Version: 7.7.0 Last Modified=06/02/2022 16:39:59
4:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Browser Info (Netscape 5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15)
5:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - URL: https://*mybucket*.s3.amazonaws.com/scorm/3d8ad71377e94884b3eea3ce04c1b827/501bc120e57d96083b050f29440c69bef3e0761c/index_lms.html?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIKJNCJSN4T6IF6DQ%2F20220602%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220602T222120Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=bb3c5b4a0068a869a4811679fe79f4dc63f0e1d398e7f4558ae60cf2ff680ae0
6:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - ----------------------------------------
7:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - ----------------------------------------
8:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In ClearErrorInfo
9:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - GetQueryStringValue Element 'StandAlone' Not Found, Returning: empty string
10:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - GetQueryStringValue Element 'ShowDebug' Not Found, Returning: empty string
11:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - strStandAlone= strShowInteractiveDebug=
12:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Standard From Configuration File - SCORM2004
13:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Using Standard From Configuration File - SCORM2004
14:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In LMSStandardAPI strStandard=SCORM2004
15:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Calling Standard Initialize
16:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In SCORM2004_Initialize
17:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In SCORM2004_ClearErrorInfo
18:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Grabbing API
19:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In SCORM2004_GrabAPI
20:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Searching with Rustici Software algorithm
21:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Error grabbing 1.2 API-SecurityError:Blocked a frame with origin "https://*mybucket*.s3.amazonaws.com" from accessing a cross-origin frame. Protocols, domains, and ports must match.
22:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - Unable to acquire SCORM API:
23:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - SCORM2004_objAPI=object
24:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In InitializeExecuted, blnSuccess=false, strErrorMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
25:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - ERROR - LMS Initialize Failed
26:Thu Jun 02 2022 19:21:30 GMT-0300 (-03) - In DisplayError, strMessage=Error - unable to acquire LMS API, content may not play properly and results may not be recorded. Please contact technical support.
27:Thu Jun 02 2022 19:24:06 GMT-0300 (-03) - In IsLoaded, returning -false

The bucket has public access, and has this CORS configuration:

[
    {
        "AllowedHeaders": [],
        "AllowedMethods": [
            "DELETE"
        ],
        "AllowedOrigins": [
            "https://*my_lms_host*",
            "https://studio.*my_lms_host*",
            "https://preview.*my_lms_host*",
            "https://apps.*my_lms_host*"
        ],
        "ExposeHeaders": []
    }
]

Any idea why can this be?

Hi Andres,

Did you get any further with this? We have the same issue.

Hi Andy, welcome to the community!
And thanks for contacting.

Unfortunately the answer is no, we couldn’t find a solution for this yet.