Web Object not appearing on iPad on SCORM Cloud

I inserted a web object onto a storyline page. It's a basic html page that is local, so it gets copied to the output folder. I publish using TinCan tracking, and upload to SCORM Cloud. When viewing on iPad, the page shows message "Content Authorization Failed", which is a msg from SCORM Cloud.

Any thoughts?

I contacted SCORM Cloud tech support and this was the response:

When using TinCan through the articulate mobile player it relies on the TinCan content specification to request content from protected sources.

Those requests look like this:

GET /ScormEngineInterface/TCAPI/ENYUU9076V/content/story_content/628QVUjlwFI_22050_56.mp3?content_token=6c4e34d4-8275-4127-a27f-857e92a07d80 HTTP/1.1
Host: cloud.scorm.com:443
Referer: app:/Articulate.swf
Proxy-Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: */*
Accept-Language: en-us
Connection: keep-alive
x-flash-version: 11,1,102,59
User-Agent: Mozilla/5.0 CPU OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9B206 Safari/7534.48.3 (iOS;

In your courses the video page is, for some reason, trying to link back to the page's location inside the course directly. The bad request, which won't have the content authorization headers outside of the browser, looks like this:

GET /content/courses/ENYUU9076V/tincan44b528f5-1114-4602-a0bd-59928e08c46a/0/story_content/WebObjects/6Eugs4AF0Qj/index.html HTTP/1.1
Host: cloud.scorm.com
Proxy-Connection: keep-alive
Accept-Encoding: gzip, deflate
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us
Connection: keep-alive
User-Agent: Mozilla/5.0 (iPad; CPU OS 6_0_1 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Mobile/10A523

My recommendation is that you contact Articulate support. They should be able to explain to you how to modify your course to utilize the content endpoint for this resource (As it is used for all of the other resources), or be able to identify a bug.

For more information on the TinCan content authorization spec take a look at the links below. The interesting bits are located under "Private Content".


1 Reply